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

define main in package.json #14

Open
rafipiccolo opened this issue Dec 14, 2024 · 0 comments
Open

define main in package.json #14

rafipiccolo opened this issue Dec 14, 2024 · 0 comments

Comments

@rafipiccolo
Copy link

import-js/eslint-plugin-import#3114

Hi,

i dont understand it fully, but it looks like the windows-1252 package currently uses the exports field in its package.json to define its entry points. However, some tools, such as eslint-plugin-import, do not yet support the exports field. This causes resolution errors when importing windows-1252.

For compatibility with such tools, could you add a main field to the package.json? For example:

"main": "./windows-1252.mjs"

This would make the package easier to use in a wider variety of environments.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant