Add exports entries without extension in package.json

[maicol07]

Hi,
can you add the export entries without extensions? This will help when using ESLint import plugin. Check the relevant discussion: import-js/eslint-plugin-import#2141

[justinfagnani]

Allowing extensionless imports would make it difficult to define compact import maps for the Lit packages. We try to make sure that our packages can work with minimal tooling, and import maps are an important piece of consuming modules with bare module specifiers in browsers without any build steps. Import maps support prefix matches, but can't add extensions.

We also couldn't change from extension-required imports to extension-less imports, as that would be a breaking change. We also can't allow more than one way to import a module because that would lead to module duplication.

Is there no way to configure the lint rule to respect the exports of the package you're importing from?

[maicol07]

No, only making extensions required will work. However, it would be better without them

[ljharb]

Why would it be difficult? Things already must parse "exports"; the presence of the extension doesn't make that more or less difficult.

Why would more than one path pointing to the same module cause duplication? Modules are cached by final filename, not by the specifier that links to it.

[maicol07]

@justinfagnani any update?