Feature request: provide a way to fix "no matching version found inside the workspace" automatically

[MichaelKapustey]

I deal with this pretty often. Resolving merge conflicts in package.json may lead to incorrectly typed version of dependency. Would be nice, if, after displaying message ' No matching version found for pkgname@1.2.12 inside the workspace' pnpm install would continue with 'found 1.3.5 instead. Would you like to update and proceed? Yes/no'

[zkochan]

You may automatically fix such issues with:

pnpm update --workspace -r

We can probably add this to the error message. Implementing a prompt sounds good to me as well.

[vallerydelexy]

not working

[Denny966]

#metoo

[maxlxq]

not working

+1

[Azoraqua]

Me too.

[zkochan]

Why don't you just use the workspace:*, workspace:~, or workspace:^ version spec to reference dependencies from the workspace? In that case the dependency will always be linked from the workspace and you'll never have to change this.

[Azoraqua]

Why don't you just use the workspace:*, workspace:~, or workspace:^ version spec to reference dependencies from the workspace? In that case the dependency will always be linked from the workspace and you'll never have to change this.

That would be the case if it worked, but for me (And apperantly a few others around here), it'll complain that the version mismatches or is not found at all. Which in turn prevents the use of pnpm almost altogether.

[craigmiller160]

I agree with the other comments. I'm not having this happen with a monorepo/workspace, I'm having this happen in general. I'm upgrading a library, and the newer version depends on a newer version of a previously installed library. the lockfile is preventing the upgrade.

[zkochan]

Until we have a reproduction available we can't fix it