Releases: standard-things/esm
Releases · standard-things/esm
0.25.1
- Dropped Node 4 code from
eval()
implementation
- Removed fragile
mtime
fast path
0.25.0
Breaking Changes
- Renamed the
"esm"
option to "mode"
0.24.0
- Aligned internal
module.loaded
of ESM more closely with the CJS API contract
- Deferred to the default
module._compile()
when no CJS compilation changes occur
- Ensured parse errors are of the user’s context
0.23.4
- Ensured temporal dead zone warnings are only triggered for
const
and let
bindings (#302)
0.23.3
- Ensured exporting named classes doesn’t throw a syntax error (#301)
- Ensured
module.parent
is only exposed if the parent allows it
- Ensured
process.mainModule
exposure is handled after determining the parse goal (#299)
0.23.2
- Continued reference equality fixes from 0.23.1 (#294)
0.23.1
- Avoided
index.js
cache creation error in some environments (#297)
- Ensured reference equality of exports is preserved with
options.cjs.interop
(#294)
- Ensured path resolution isn’t mixed up by dual packages (#296)
0.23.0
Breaking Changes
- Raised minimum support to Node 6+
Other Changes
- Added support for live bindings of CJS exports with
options.cjs.namedExports
- Ensured dual packages are supported (#286)
0.22.0
- Added support for new Node ESM rule to treat extensionless files as CJS
- Enabled sharing global paths,
process
data, and URI methods across loader instances
- Ensured
safeGetenv
is used for process.env
access when available
- Made the loader run in a new context to avoid pollution of builtin prototypes
- Removed gzip module support
0.21.7
- Ensured Node’s
--print
flag works (#279)