-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Better Corepack support #566
Comments
Would be nice if it could be run automatically - perhaps when detecting that the shims are already there? |
Hi! sorry for the delay.
By
Where would this configuration go?
I think my next question would be, why shouldn't it be the default? Will it hurt to call
intriguing. Maybe we can have a
|
After a fresh install.
Both of these seem fine. Having
Corepack is currently marked "Stability: 1 - Experimental" by Node.js and is explicitly opt-in because of this:
Until it's more stable I don't think Corepack should be the default for fnm. |
I personally think it could be interesting! The main reason why it's not the default yet isn't stability per-se (as in, I'm not aware of any bugs in it), but rather that it's a little difficult to evaluate the risks for the whole Node userbase. Enabling it by default for a smaller population (such as fnm users) would be a good way to gather confidence. |
Friendly ping 😊 |
This would be extremely helpful in making it easier to onboard new developers to fnm |
Corepack is an official Node.js tool for managing package managers like npm, pnpm, or Yarn.
It has been bundled with Node.js versions since v16.9.
Instead of running
npm i -g yarn
, you runcorepack enable
. This placesyarn
+pnpm
binaries (technically they're Corepack shims) alongside thenode
binary.Unfortunately, switching to a new Node.js version with fnm requires you to run
corepack enable
again before you can use your custom package managers.Could a configuration option (ex.
--corepack
) be added to automatically handle this for users?Related: post-install hooks like in #139 could be used to run
corepack enable
, although it might be good to have a dedicated option for Corepack since it's going to be a very common workflow for Node.js usersThe text was updated successfully, but these errors were encountered: