| pnpm.io | rfcs | |
|---|---|---|
| 1 | 35 | |
| 193 | 716 | |
| 2.1% | 0.3% | |
| 9.5 | 5.7 | |
| 7 days ago | 17 days ago | |
| JavaScript | JavaScript | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pnpm.io
-
Yarn 4.0
An update on this:
After talking to one of the contributors on Discord, it seems that they have a special "deploy" command for exactly this (copying files and dependencies for a single workspace package) which I had overlooked since the documentation for it wasn't so self explanatory, they have now updated the docs for this command [1] and opened a PR to update the docs for the Monorepo Docker example to use it instead [2].
I have to say I'm impressed with how responsive the maintainers were to my question, and this `pnpm deploy` workflow does actually make sense to me.
[1] https://github.com/pnpm/pnpm.io/commit/3e6cb7b2cdaf23a423c31...
[2] https://github.com/pnpm/pnpm.io/pull/469
rfcs
-
Yarn 4.0
npm workspaces plus Wireit works far better than Lerna, in my experience.
https://github.com/google/wireit
Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and it's long-running service script support make it much more useful and comprehensive than Lerna.
I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706
-
NPM vs Yarn?
It's coming https://github.com/npm/rfcs/blob/main/accepted/0042-isolated-mode.md
-
How do you know that the .exe or .apk file for an open source software on github is actually compiled from the viewable source code?
This just got accepted as a proposal in NPM: https://github.com/npm/rfcs/pull/626
-
Why aren't Node.js package managers interoperable?
npm also plans to support pnpm-style node_modules
-
Axios shipped a buggy version and it broke many productions apps. Let this be a lesson to pin your dependencies!
(I usually end up removing npm ci from CI/CD since I think it is way too slow and want to cache node_modules from previous builds; I'm waiting for https://github.com/npm/rfcs/issues/415 to land to make this fail-safe npm install --from-lockfile. Yarn does support this already)
- How to run multiple NPM commands simultaneously using concurrently
- [RRFC] Parallel script execution when value is set to an array of text. · Issue #610 · npm/rfcs
- Lerna has gone. Which Monorepo is right for a Node.js BACKEND now?
- NPM introduces a new Dependency Selector Syntax
-
How to respond to growing supply chain security risks?
I started following this problem from the discussion at npm about making install scripts opt-in. But install scripts are not the only threat, there are more ways for malicious actors:
What are some alternatives?
pacquet - experimental package manager for node.js
vm2 - Advanced vm/sandbox for Node.js
orogene - Makes `node_modules/` happen. Fast. No fuss.
pnpm - Fast, disk space efficient package manager
setup-bun - Set up your GitHub Actions workflow with a specific version of Bun
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
pn - This is an experimental wrapper over the pnpm CLI written in Rust
Cargo - The Rust package manager
GHSA-g2q5-5433-rhrf
wireit - Wireit upgrades your npm/pnpm/yarn scripts to make them smarter and more efficient.
feedback - Public feedback discussions for npm