define main in package.json

[rafipiccolo]

import-js/eslint-plugin-import#3114

Hi,

i dont understand it fully, but it looks like the linky 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 this package.

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

"main": "./dist/lib/index.js"

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

Thank you!

[bokub]

Hi @rafipiccolo

I'm quite surprised, "exports" is pretty standard, and it what the Node.js documentation recommends.

However, I don't mind adding a "main" field if it can help your

If both "exports" and "main" are defined, the "exports" field takes precedence over "main" in supported versions of Node.js.

Do you want to open a pull request ? You can add the "main" field and bump the patch version

[rafipiccolo]

thx, here is the PR: #74

[JounQin]

Try https://github.com/import-js/eslint-import-resolver-typescript or https://github.com/un-ts/eslint-plugin-import-x