cotton
ni
| cotton | ni | |
|---|---|---|
| 15 | 14 | |
| 300 | 6,548 | |
| - | 2.0% | |
| 9.3 | 8.1 | |
| 6 days ago | 23 days ago | |
| Rust | TypeScript | |
| GNU General Public License v3.0 only | MIT License |
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.
cotton
- A package manager for JavaScript projects. With a fast network, `cotton install` runs faster than `rm -rf node_modules`.
-
I re-ran their benchmarks. Cotton ran several times faster than other package managers, taking less than 2 seconds without any cache.
I recently found Cotton, an alternative to npm or yarn.
-
Has anyone else ever tried this? `cotton install` is only slightly faster than `rm -rf node_modules`, not as fast as they claim. I guess it can save a bit here and there, but I don't see the point.
Does anyone else use Cotton? I'm the lead developer for 3 different web applications, and package installation is only a small part of building (only takes ~1 minute). Saving 1 minute on a 10 minute build wouldn't be that important.
ni
-
Rsbuild – A Better Vite?
It's supposed to be webpack plugin-and-API compatible, so if you already use webpack, hopefully not (much).
But is this constant turnover getting ridiculous in the web dev & JS ecosystem?
Yes. I simultaneously credit and blame facebook for starting it with yarn; after yarn, the trend of re-writing build tools seemed to become much more acceptable and trendy, especially since yarn (at the time) was multiple times faster than npm; you could argue it was worth it. But now we've reached a stage where the diversity of tools like npm, yarn and pnpm, now tools like ni (https://github.com/antfu-collective/ni) are emerging to manage the diversity.
I think this is getting out of hand, now there are n+1 of them.
-
Show HN: Px – Run commands across different JavaScript package managers
this is awesome! how would you contrast this with https://github.com/antfu-collective/ni?
-
Não se preocupe mais com o package manager do seu projeto NodeJS
View on GitHub
- GitHub - antfu/ni: 💡 Use the right package manager
-
antfu/ni helps you select the right package manager
Repo: https://github.com/antfu/ni
-
Never Use the WRONG Package Manager Again!
Here's a description of all currently supported commands. In case something changes and this gets outdated, you can always check the full list on the project's README.
-
TypeScript tooling and ecosystem
I highly recommend using https://github.com/antfu/ni to not care about if the project uses npm/yarn/pnpm
-
Say Goodbye to Package Manager Chaos with ni
By using ni, you can save yourself a lot of time and avoid the frustration of dealing with conflicting lock files and dependencies. So if you haven't already, give ni a try — you won't regret it!
-
How do you manage projects using different package managers?
You might want take a look at ni by antfu: https://github.com/antfu/ni
What are some alternatives?
zap - Another [insert blazing fast synonyms] JavaScript package manager
npm-quick-run - Quickly run NPM script by prefix without typing the full name
swpm - Switch Package Manager - Say goodbye to Package Manager confusion
ny - 🗽 Fast, Proxy Package Manager for JavaScript
importly - import map generator
snm - 🤏 Smol and simple node version manager written in rust 🦀
ultra-runner - 🏃⛰ Ultra fast monorepo script runner and build tool
verdaccio - A lightweight Node.js private proxy registry
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
commonmark-spec - CommonMark spec, with reference implementations in C and JavaScript
xum - 🤹 Extremely Universal Manager - A script that unifies all Node package managers