EnvGap
Remove `module` field in `package.json`
envgap__dcastil__tailwind-merge-285
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
cb8fabe290f2fb6c470303cbdfba7be79d59af27- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
dcastil/tailwind-merge #285 · read the original issue
The `module` field was used for ESM builds by bundlers before there was `type: module`, but because of `type: module`, the `module` field never became a standard. Instead, [package exports](https://nodejs.org/api/packages.html#exports) can be used to define entry points for different environments which I already use. As `module` is not a standard and bundlers and Node 12+ support the `exports` field, there is no reason to keep it. More info: - https://stackoverflow.com/questions/42708484/what-is-the-module-package-json-field-for/42817320#42817320 - https://esbuild.github.io/api/#main-fields:~:text=CommonJS%2Dstyle%20module.-,module,-This%20field%20came
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]