corepack
pacquet
| corepack | pacquet | |
|---|---|---|
| 5 | 2 | |
| 2,151 | 748 | |
| 3.6% | 0.1% | |
| 8.9 | 9.3 | |
| 6 days ago | 3 months ago | |
| TypeScript | Rust | |
| MIT License | Apache License 2.0 |
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.
corepack
-
Yarn 4.0
I'd love to use Bun for my projects, but it's not integrated into Corepack yet (and therefore you cannot pin the bun version w/ checksum in package.json)
https://github.com/nodejs/corepack/issues/295
- corepack global package?
-
Every NPM package potentially compromised
Recently Node 16 LTS cycle started. One month and a few days before the carry-over, a super controversial package titled `coredeps` [0] was officially declared a core module and has been bundled with all official distributions since.
The NodeJS team refuses to discuss NPM because it's a separate 3rd party. And yet.... this NodeJS Core module comes pre-installed as a global NPM package.
We're just getting started.
This module installs or even reinstalls any supported package manager when you execute a script with a name that would match any that they'd recognise. Opt-in for only a short period, and intending to expand beyond package manager installations.
Amidst all that's been going on, NPM (Nonstop Published Moments) is working on a feature that silently hijacks user commands and installs foreign software. The code found in those compromised packages operated in a similar manner and was labeled a critical severity vulnerability.
The following might actually make you cry.
Of these third party remote distributions it's downloading, the number of checksum, keys, or even build configurations that are being verified is 0.
The game that Microsoft is playing with their recent acquisitions here is quite clear, but there's too much collateral damage.
[0] https://github.com/nodejs/corepack#readme
-
Corepack: the Node.js' manager of package managers
The new Node.js LTS v16 will be released at the end of October (without a fancy name assigned yet), it'll have Corepack preinstalled in the default configuration since v16.9.0. 👌
-
Yarn 3.0 🚀🤖 Performances, ESBuild, Better Patches, ...
Corepack integration
pacquet
-
Yarn 4.0
b) use syncpack to ensure all your dependencies in different workspaces use the same versions. This doesn't need to be done in the package manager.
pnpm also has pnpm licenses to help keep compliance happy.
If someone wants to write a package manager in Rust for speed (pnpm is already moving in this direction, see https://github.com/pnpm/pn and https://github.com/pnpm/pacquet ), we'd take a look. Otherwise - not enough benefit to switching away.
- Experimental Package Manager for Node.js
What are some alternatives?
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
pnpm.io - pnpm's website
npm
pn - This is an experimental wrapper over the pnpm CLI written in Rust
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
setup-bun - Set up your GitHub Actions workflow with a specific version of Bun
vscode-deploy-reloaded - Recoded version of Visual Studio Code extension 'vs-deploy', which provides commands to deploy files to one or more destinations.
wireit - Wireit upgrades your npm/pnpm/yarn scripts to make them smarter and more efficient.
berry - 📦🐈 Active development trunk for Yarn ⚒
pnpm - Fast, disk space efficient package manager
node - Node.js JavaScript runtime ✨🐢🚀✨
orogene - Makes `node_modules/` happen. Fast. No fuss.