Module subpath doesn't resolve about import-from-esm HOT 5 CLOSED

Hi @lukiffer, sorry you're encountering an issue with this package!

Could you please run the failing command with the DEBUG=import-from-esm env variable? This will log every path it has tried to resolve.

from import-from-esm.

Here's the actual output: https://gist.github.com/lukiffer/fd3f0b38960555b7bb808fdb5edc42f7

(I think) the issue is with the first resolve attempt:

Trying to resolve '@bdrk/semantic-release-config/npm'

In this case, a file does in fact exist at node_modules/@bdrk/semantic-release-config/npm/index.js but is throwing ERR_MODULE_NOT_FOUND.

Moving the file to ./npm.js (with type="commonjs" in package.json) or moving it to ./npm.cjs both work fine. So it seems like it's either not trying the index.js default, or having some trouble locating it.

from import-from-esm.

Ok, I found the issue. I'm working on a fix and should be releasing that in the next few hours, will keep you updated. Thanks for the heads up!

from import-from-esm.

🎉 This issue has been resolved in version 1.3.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from import-from-esm.

Renovate should update the dependency on the various @semantic-release repos in the next few hours!

Feel free to reopen if you're still getting an issue after upgrading 😄

EDIT: forgot @semantic-release repositories didn't use pinned versions, so you just need to update your lockfile with npm update import-from-esm, but it seems you're using npx to run semantic-release so none of the above should be needed :)

from import-from-esm.