-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERR_REQUIRED_ESM error with multiple plugin packages #138
Comments
Same problem. Thanks for making this issue. |
Confirming that I also only get this error when using semantic-release-monorepo. When I remove the |
I published a new package semantic-release-monorepo-esm that supports esm. v1.0.10 should work without issues. |
@bryanjtc That's awesome. I was thinking it might make sense to fork this. I'll play around with it. |
@jcapogna NPM package: https://www.npmjs.com/package/@rimac-technology/semantic-release-monorepo |
@mario-jerkovic That's great! I'll check it out. @pmowrer If one of these forked packages works well, maybe we should deprecate this package and point it to the fork since this package is no longer maintained. Are there any major differences between semantic-release-monorepo-esm from @bryanjtc and https://github.com/RimacTechnology/semantic-release-monorepo from @mario-jerkovic ?? |
This package is a rewrite, it doesn't need the Except those two thing, everything else should work same as before 🙂 |
🎉 This issue has been resolved in version 8.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
It has been documented in a few places like #136 that certain semantic-release plugins need to be downgraded when using semantic-release-monorepo, due to it not support ESM yet. ESM support should be added in #137.
I'm creating this ticket to consolidate knowledge about this problem for other people.
So far I have to add perform the following downgrades:
The text was updated successfully, but these errors were encountered: