feat(version): reify on workspace version change

[ruyadorno]

Adds a minimalistic reify step that updates the installed tree after a
version change within one of the configured workspaces when using any
of the workspaces config options.

It's also possible to use the --save config option in order to
auto update semver ranges of dependencies declarations accross dependent
package.json files.

References

Fixes: #3403
Relates to: npm/rfcs#556
Relates to: #3757
Relates to: #4193

[nlf]

these changes look good to me, however i do think it's probably a good idea to document this more explicitly in the workspaces docs with examples of exactly what will happen when it's used.

that can be a follow up pull request, though, so i'm marking this approved as-is

[ruyadorno]

Thanks @nlf that's a great idea! I know that page is in need of some love, I was chatting with @bnb the other day that was also noticing it could use more consistent naming across the examples there.

With that in mind I'll pb take the time this week to work on a small revamp/clean up of that page and will make sure to also add examples and notes about this behavior 🤔 although it might be better to land these doc updates after we also add this similar behavior to npm init and any other command that can use this immediate reify step when operating in workspaces, anyways something we can chat about in a diff PR 😊

[Regaddi]

Sorry to come back to this PR so late, but I think I just noticed this new behavior.

Does this change mean it's no longer possible to do a very simple npm version patch bump that will only bump the "version" field in a package's package.json?

[manuth]

@fritzy I just stumbled accross this PR because I still have issues with npms version behavior in workspaces.

In workspace-a I have added workspace-b as a dependency. When running npm version, the workspace-b dependency inside workspace-as package.json file isn't getting updated. Only dependencies inside the root workspace-test are being updated.

Thus, I wouldn't consider #3403 as closed.

Anyhow - thanks a ton for the great work, this is highly appreciated.

Steps to reproduce

1. Create a root package.json:

   package.json:

   {
       "name": "workspaces-test",
       "version": "1.0.0",
       "workspaces": [
           "workspace-a",
           "workspace-b"
       ],
       "dependencies": {
           "workspace-a": "^1.0.0",
           "workspace-b": "^1.0.0"
       }
   }

2. Create package.json files for the workspaces:

   workspace-a/package.json:

   {
       "name": "workspace-a",
       "version": "1.0.0",
       "dependencies": {
           "workspace-b": "^1.0.0"
       }
   }

   workspace-b/package.json:

   {
       "name": "workspace-b",
       "version": "1.0.0"
   }

3. npm install the workspace root

4. Run npm version:

   npm version -ws 2.0.0
   

5. Inspect the result

   • Take note that the workspace-a and workspace-b dependencies inside the root package.json have been updated properly.
   • In workspace-a/package.json, take note, that the workspace-b dependency did not update and still is ^1.0.0 instead of ^2.0.0.

[ruyadorno]

Sorry to come back to this PR so late, but I think I just noticed this new behavior.

Does this change mean it's no longer possible to do a very simple npm version patch bump that will only bump the "version" field in a package's package.json?

@Regaddi There's a --no-workspaces-update or workspace-update=false in .npmrc file escape hatch included in the original implementation.

[necolas]

I was looking for this feature and had the same problem as @manuth with the option seemingly not working to update the versions of the package in dependencies within the workspace root.