Type of Change
Summary
A part of #820 / #832, wanted to capture a follow up issue to capture an enhancement for dependencies that assume directory level index.js files will auto resolve and are not captured in an export map
import { foo } from 'some-package/lib'; // where it _actually_ exists at 'some-package/lib/index.js'Details
Discovered this as part of testing a Stencil integration and found this particular scenario happening. @stencil/core in this case has an entry point ultimately points to a file with no file extension.
import { BUILD, NAMESPACE } from '@stencil/core/internal/app-data';The directory does have an index.js so there is that to use / check for, as well as a package.json, so seems like we should be able to do something with either of those.
Should also file this with the Stencil team as well.
Type of Change
Summary
A part of #820 / #832, wanted to capture a follow up issue to capture an enhancement for dependencies that assume directory level index.js files will auto resolve and are not captured in an export map
Details
Discovered this as part of testing a Stencil integration and found this particular scenario happening. @stencil/core in this case has an entry point ultimately points to a file with no file extension.
The directory does have an index.js so there is that to use / check for, as well as a package.json, so seems like we should be able to do something with either of those.
Should also file this with the Stencil team as well.