@yarnpkg/pnpify
Advanced tools
Changelog
4.1.0
Tweaks -,--verbose in yarn workspaces foreach; -v will now only print the prefixes, -vv will be necessary to also print the timings.
Adds a new --json option to yarn run when called without script name
Fixes node-modules linker link: dependencies mistreatment as inner workspaces, when they point to a parent folder of a workspace
Fixes spurious "No candidates found" errors
Fixes missing executable permissions when using nodeLinker: pnpm
Fixes packages being incorrectly flagged as optional
Fixes cache key corruptions due to uncontrolled git merges
Fixes yarn version apply --all --dry-run making unexpected changes
Fixes yarn npm login when the remote registry is Verdaccio
Readme
A CLI tool designed for running commands with a virtual node_modules folder.
yarn add -D @yarnpkg/pnpify
pnpify run - Run a command with a virtual node_modules folder.FAQs
Unknown package
The npm package @yarnpkg/pnpify receives a total of 16,554 weekly downloads. As such, @yarnpkg/pnpify popularity was classified as popular.
We found that @yarnpkg/pnpify demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team has identified a malicious Python package that is typosquatting the popular crytic-compile utility, frequently used in popular toolkits and development environments for smart contracts and crypto applications.
Security News
NIST updates on the NVD backlog after media reports that over 50% of KEVs were unenriched since mid-February. They've contracted additional support and partnered with CISA to clear the backlog by fiscal year-end.
Security News
A hospital in Mobile, Alabama, agreed to a settlement in a landmark ransomware death lawsuit, but is now reportedly reconsidering the agreement and refusing to pay.