feat: bump pnpm and adopt the "catalog" feature #28110
Conversation
|
|
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
|
This looks great to me - we just need the following two issues to be resolved: |
|
sure. ill keep an eye on those, update this PR, and let you know when ready. |
🔗 Linked issue
Resolves #28109
📚 Description
Maintaining unique dependency versions in a workspace is easier with catalogs, preventing runtime conflicts, reducing bundle size, simplifying upgrades by editing a single catalog entry, and minimizing git merge conflicts.
Caveats
The pnpm update command does not yet support catalogs.
To update dependencies defined in pnpm-workspace.yaml, newer version ranges will need to be chosen manually until a future version of pnpm handles this.