loose-envify is a fast, “loose” selective replacer for `process.env` in JavaScript, similar to envify but much faster, implemented using `js-tokens` instead of an AST. It is useful for build-time inlining of environment variables, with limitations such as not handling broken syntax and not supporting template strings that reference `process.env` inside embedded expressions.
Project status
- The GitHub source
zertosh/loose-envifyappears quiet and likely in maintenance mode, with no update activity reflected in the provided recent version history sincev1.4.0(2018-07-10), and the last upstream push noted as 2020-12-18. - The update cadence is very low, with large multi year gaps between tagged updates (for example, 2015-2016, then 2017, then 2018), which suggests limited ongoing development.
AI summary generated
Recent updates
v1.4.0
Release v1.4.0 updates the package version and loosens the allowed dependency range for js-tokens. No release notes were provided, so the only documented scope comes from the code diff in package.json.
Breakingv1.3.1
v1.3.1 contains a dependency upgrade and a corresponding code change in the runtime import of js-tokens. No release notes were provided for this version, so the only observable changes are from the code diff itself.
v1.3.0
Release v1.3.0 was published on 2016-10-28, but no release notes were provided by the publisher. As a result, this release cannot be assessed from the notes for new features, breaking changes, bug fixes, or security updates.
v1.2.0
Release v1.2.0 updates loose-envify with a new executable CLI and adjusts benchmark and internal output generation. The provided release notes are empty, so the documented vs actual change comparison depends on code inspection only.
Featuresv1.1.0
No release notes were provided for v1.1.0. The code changes primarily refactor the internal environment replacement logic by moving it from `loose-envify.js` into a new `replace.js` module, while bumping the package version to 1.1.0.
v1.0.0
This release is tagged v1.0.0, but no release notes were provided by the publisher. As a result, there is no documented information about new features, fixes, breaking changes, or migration steps.