a `Cannot read properties of null (reading 'matches'` error when using multi-semantic-release

[arvinxx]

a `Cannot read properties of null (reading 'matches'` error when using multi-semantic-release

[arvinxx]

relative issue: npm/cli#4367

[travi]

given that issue in npm, this sounds unrelated to the npm plugin for semantic-release specifically. can this issue be closed, or is there something i'm overlooking that relates it specifically to this plugin?

[arvinxx]

given that issue in npm, this sounds unrelated to the npm plugin for semantic-release specifically. can this issue be closed, or is there something i'm overlooking that relates it specifically to this plugin?

maybe you can try catch this error here? https://github.com/semantic-release/npm/blob/master/lib/prepare.js#L22

[travi]

could you help me understand the context of the situation where this would happen when publishing a release? why are linked packages involved in your release pipeline?

[arvinxx]

could you help me understand the context of the situation where this would happen when publishing a release? why are linked packages involved in your release pipeline?

when before publish, npm version is called to upgrade package version (https://github.com/semantic-release/npm/blob/master/lib/prepare.js#L10). In npm v7, it works well. But in npm v8, npm use @npmcli/arborist during npm version. @npmcli/arborist package causes the error, but version actually is bumped. So I think it can be try catch.

[travi]

semantic-release is used by many to publish packages using npm v8. i'm trying to understand what is different about your project that results in this error. the issue you linked to suggests it is related to linked packages, but you havent answered my question about my there are linked packages in your project when releasing.

[arvinxx]

semantic-release is used by many to publish packages using npm v8. i'm trying to understand what is different about your project that results in this error. the issue you linked to suggests it is related to linked packages, but you havent answered my question about my there are linked packages in your project when releasing.

i use pnpm workspace for a monorepo(here it is: https://github.com/arvinxx/gitmoji-commit-workflow ). and pnpm use link package to relate package.

[travi]

ah, ok. that makes sense. semantic-release does not officially support monorepos because of the additional complexity it can add, such as this situation. we attempt to avoid breaking the ability to build monorepo support on top of our core, like with multi-semantic-release, but solving monorepo specific use cases is out of scope for this project.

without npm providing more information about the reason for the failure, there isnt much that we could do in this plugin if we were to catch the error because we wouldnt be able to distinguish from other errors that should be handled in other ways.

the issue referenced above mentions a recommended fix within project impacted by this situation. it may be possible for multi-semantic-release to handle configuring your project according to that recommendation. regardless, this appears to be more related to npm and multi-semantic-release in the context of your pnpm project. since that is a configuration that is out of scope for this project, i'm going to close this issue. it may make more sense to open an issue against multi-semantic-release instead.