You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: