Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove module field in package.json #285

Closed
dcastil opened this issue Aug 18, 2023 · 1 comment · Fixed by #289
Closed

Remove module field in package.json #285

dcastil opened this issue Aug 18, 2023 · 1 comment · Fixed by #289
Labels
breaking Is breaking change context-v2 Related to tailwind-merge v2 feature Is new feature
Milestone

Comments

@dcastil
Copy link
Owner

dcastil commented Aug 18, 2023

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 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:

@dcastil dcastil added breaking Is breaking change feature request labels Aug 18, 2023
@dcastil dcastil added this to the v2 milestone Aug 18, 2023
@github-actions
Copy link

This was addressed in release v2.0.0.

@dcastil dcastil added the context-v2 Related to tailwind-merge v2 label Oct 30, 2023
@dcastil dcastil added feature Is new feature and removed feature request labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Is breaking change context-v2 Related to tailwind-merge v2 feature Is new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant