-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error [ERR_REQUIRE_ESM]: require() of ES Module #221
Comments
I have the same issue ever since v1.2.x releases. At first, I thought it was my configuration since the plugin had been renamed but even after fixing all these issues the problem persists rendering my previously working release workflow completely unusable. Any help would be appreciated. |
It should be possible to downgrade to I also encountered this issue and compared it with the last successful deploy and it was I think there is a fix for this on the way here: #222 Thanks |
Please try |
@jpoehnelt I am not seeing OP's issue resolved as of the latest (1.2.6) release. Am I missing something? |
Same here, same issue with 1.2.5 |
Please try https://www.npmjs.com/package/semantic-release-replace-plugin/v/1.2.7 which includes changes from 90c2976. |
@jpoehnelt Thanks. Just to highlight, this version requires:
If anyone want to resolve the issue and not want to change the dependencies, then i suggest to install the earlier working version (
|
@KennyLindahl Please note that these are the same settings used by many of the most popular semantic release plugins at this time. |
Closing this as there have been no reports. Please comment if you have an issue with |
thanks for all the work on this lib @jpoehnelt ! |
Hi everyone!
running semantic-release in dry-run mode is raising the following error:
I am not super familiar with nodejs ... any idea about what is happening?
thanks!
The text was updated successfully, but these errors were encountered: