The automated release is failing 🚨

[kamranayub]

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot :package::rocket:

[kamranayub]

So a chicken or the egg issue:

• Using pkgRoot in @semantic-release/npm will look for package.json in dist folder
• The package.json is in the root
• Using the prepare script will generate an extra dist/dist/ folder because it runs both after installing and prepublishing time IN the dist working directory

I will try maybe just a postinstall to get it in place OR I can add a yarn script to run during CI only.

[kamranayub]

That worked but I am not convinced that is the best either because postinstall happens on the consumer end too. Maybe just baking it into the CI workflow or a yarn script is the answer then. 🤷‍♂️