canirequire

canirequire › CommonJS › loose-envify

Is loose-envify ESM-only? Can you require() it?

Fast (and loose) selective `process.env` replacer using js-tokens instead of an AST

Last verified Sep 9, 2026 against loose-envify@1.4.0. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

loose-envify ships CommonJS only. require("loose-envify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "loose-envify" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

What to do

  1. require("loose-envify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
  2. From ES modules use the default import: import looseEnvify from "loose-envify"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for loose-envify; declare the module yourself if you need them.
Latest
1.4.0 (Jul 10, 2018)
Module format
CommonJS
Last CommonJS version
1.4.0
TypeScript types
None
Node engines
not declared
Weekly downloads
65.0M
License
MIT

Does loose-envify@1.4.0 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("loose-envify") from a CommonJS file and import "loose-envify" from an ES module.

Runtimerequire("loose-envify")import "loose-envify"
Node.js 18✓ works✓ works
Node.js 20✓ works✓ works
Node.js 22✓ works✓ works
Node.js 24✓ works✓ works
Node.js 26✓ works✓ works
Bun 1.4.0✓ works✓ works

How to import loose-envify

ES modules (import)

import looseEnvify from "loose-envify";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const looseEnvify = require("loose-envify");

Module format by version

Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (6 versions; the newest 6 shown).

VersionsFormatFirst published
1.0.0 – 1.4.0CommonJSSep 21, 2015

Frequently asked

Is loose-envify ESM-only?

loose-envify@1.4.0 is a CommonJS package. loose-envify ships CommonJS only. require("loose-envify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "loose-envify" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

Can I import loose-envify with ES module syntax?

Yes. import looseEnvify from "loose-envify" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

Does loose-envify work in Bun?

Yes. import "loose-envify" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does loose-envify ship TypeScript types?

No. loose-envify ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity