You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[23:29:24] [semantic-release] » × ENOPKGNAME Missing `name` property in `package.json`.
The package.json's name (https://docs.npmjs.com/files/package.json#name) property is required in order to publish a package to the npm registry.
Please make sure to add a valid name for your package in your package.json.
AggregateError:
SemanticReleaseError: Missing `name` property in `package.json`.
The text was updated successfully, but these errors were encountered:
I was going to write something like "isn't name required" but today I learned it's not required if the package isn't published as would be the case with a monorepo root package. By convention I've always used a -monorepo suffix (e.g foobar-monorepo) for the root package name and set private to true to prevent any accidental publish.
Do you have any suggestions how this could be implemented? If package.json is modified semantic-release would throw an error that the working copy is dirty.
If this plugin can override this semantic-release rule, maybe follow the convention to let name empty but made warning for private at true for prevent accidental publishing.
Like
version
, how can we prevent this error?The text was updated successfully, but these errors were encountered: