EnvGap
node exports?
envgap__guybedford__es-module-lexer-54
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
28175f194ecc6506896bc942938f4e8c01e3cfb8- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
guybedford/es-module-lexer #54 · read the original issue
hey,
I remember we added and then reverted exports to the package.json...
I'm not sure however what the reason was?
Right now I am trying to import es-module-lexer in a node 14+ type="module" package and I need to do
```js
import { init, parse } from 'es-module-lexer/dist/lexer.js';
```
would be nice if I could just do
```js
import { init, parse } from 'es-module-lexer';
```
this could be archived with an export map that may look something like this
```js
"exports": {
".": {
"require": "dist/lexer.cjs",
"default": "dist/lexer.js",
}
}
```
so the question is could we add it? and if not why was that again 😅04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]