I usually post about tech here, but today it's something else.
The country I grew up in, India, is seeing peaceful protesters being brutally beaten. There are multiple reports and international news outlets covering this.
Please help spread awareness 🙏
https://t.co/FgA4a1JUvf
My wishlist: #nodejs follows macOS/iOS versioning, and releases one version per year.
Drop October major version releases.
We can start with 26 in April 2026.
It'll be aligned with calendar year too!
@mbetts@Meligy@rauchg@theo You can also replace "corepack enable" command with "npm i -g corepack" and your setup will continue to work as it did before.
@Meligy It's sad that corepack is being removed from Node.js
But your setup will continue to work if you replace "corepack enable" command with "npm i -g corepack"
@andrejnsimoes Corepack will still be available on npm.
You just need to replace `corepack enable` command with `npm i -g corepack`
Do contribute to it's continued development, i.e. triaging issues, review PRs etc!
For details, check https://t.co/laveRzsGUu
@NodeSource It doesn't had any significant impact on my workflow.
I've already switched to globally install corepack in my workspaces and CI, as it's documented in both yarn and pnpm docs.
i.e. as easy as replacing "corepack enable" command with "npm i -g corepack"
@JonasDoesThings@styfle That's okay. Decisions happen for many reasons, and we need to move on.
If you like corepack, do volunteer to maintain it, i.e. triage issues, review PRs etc.
It's not going away. It's just removed from Node.js v25+, but will be available on npm
Details https://t.co/PaSYfypGW4
@realsteelbrain@styfle Join the other volunteers to maintain corepack, i.e. triage issues, review PRs etc.
It's only being removed from Node.js distribution from v25+. You can still install it globally from npm, and it'll continue to work the same way!
Details https://t.co/PaSYfypGW4
@TheChapeleiro@styfle It's not. You can globally install corepack from npm and it'll work. There's no difference in the experience.
Actually, you'll get the latest version of corepack which will contain any bug fixes while might have existed in the version bundled inside Node.js
@bronifty @capajj@shellscape@styfle@PavitraGolchha@BUN@pnpmjs You can also ask your CI provider to make it wasy to enable corepack.
Here's a request on GitHub action used to setup node https://t.co/xUHFrYkc6G
@bronifty @capajj@shellscape@styfle@PavitraGolchha@BUN@pnpmjs Do continue using corepack by installing it from npm!
If you have time, please volunteer to maintain it, i.e. triage issues, review PRs etc.
Details https://t.co/PaSYfypGW4
@reid Corepack will still be available on npm, it'll just stop getting distributed in Node.js v25 onwards.
If you like corepack, please volunteer to maintain it, i.e. triage issues, review PRs etc.
Details https://t.co/PaSYfypGW4
@mmateonunez Please volunteer to maintain corepack, i.e. triage issues, review PRs etc.
I asked the corepack maintainers what's required for it's continued development, and that was their answer.
https://t.co/PaSYfypGW4
@grok@Hacksore@styfle Grok is incorrect in-part here.
Developers actually enjoy automatic installation of package managers by corepack. Those who prefer to manually install their package manager versions can continue doing even after enabling corepack.
If you care about Corepack’s future and want to ensure continued development, let’s keep the conversation going! Huge thanks to @trivikram for raising this important discussion:
https://t.co/L45OOYfsVQ
@advaithj1@wunderacle I created an issue to find what's needed for its continued development outside of Node.js distribution.
Do subscribe to the issue and upvote/comment if you're interested.
https://t.co/laveRzsGUu