Upgrade to Yarn v3 #119
Upgrade to Yarn v3 #119
Conversation
|
🚨 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 new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. What is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. 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 should be resolved in #117. |
mcmire
force-pushed
the
upgrade-to-yarn-v3
branch
from
3961ad8 to
ea79f6a
Compare
- Use Yarn 3.2.1 as designated by the module template - Regenerate `yarn.lock` using Yarn v3 - Replace `prepublishOnly` package script with `prepack`, and add `scripts/prepack.sh` from the module template - Run `yarn dedupe` when running `yarn lint` - Remove `yarn setup` as `yarn install` automatically runs `yarn allow-scripts`
mcmire
force-pushed
the
upgrade-to-yarn-v3
branch
from
ea79f6a to
868f177
Compare
| "@babel/plugin-transform-runtime": "^7.5.5", | ||
| "@babel/preset-env": "^7.5.5", | ||
| "@babel/runtime": "^7.21.0", |
There was a problem hiding this comment.
yarn install seems to have applied this. I guess dependencies are alphabetized in Yarn v3.
|
Double-checked that this doesn't affect |
yarn.lockusing Yarn v3prepublishOnlypackage script withprepack, and addscripts/prepack.shfrom the module templateyarn dedupewhen runningyarn lintyarn setupasyarn installautomatically runsyarn allow-scripts