Create .npmrc / pnpm-workspace.yaml file in current project root, with pnpm specified configuration and default value.
Install workspace root dependencies only(as pnpm doesnot support this, we collect dependencies from workspace root and install them).
Select a set of packages, and install dependencies for them.
Select a workspace package, and then select script to execute and filtering type.
script selection items come from selected package's package.json file and workspace-only extra scripts(see Workspace.ExtraWorkspaceScripts).
filtering types come from the filtering syntax supported by pnpm now:
This command will ask you for the release type(major, minor, ...), and some publish related opitions( git-checks , tag, ...) , and update the bumped version in package.json 's version field, then run pnpm publish with arguments composed from prompt result.
you can choose release type which follows semver type, or input new version manually.
we ask tag, access, git-checks, for final command arguments.
Similar to the publish-node-package command, but this command requires you to select a workspace package to release.
This command collects all deps included in root packages.json, and display quick pick prompt for you to select from.
Selected dependencies will be removed by pnpm remove command.
This command is also avaliable in non-workspace project.
Similar to remove-workspace-root-deps, but this command requires you to select a workspace package first.
This command will update dependencies of your selected package by pnpm update command, related options will also be prompted for arguments composing.
This extra scripts command helps you to create pre-configured npm scripts, which will used by select-workspace-package command.
This can be useful when you want to run some scripts which only exist in dependencies or dependents of selected package.
In .npmrc, this extension provides completion for both key and value(only pnpm specified configurations are included).
In pnpm-workspace.yaml, this extension provides key completions and hovers.
In package.json, the dependency item with workspace: protocol will have Click to open workspace package folder codelen, you can click it to open target package.