-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow XDG Specification #145
Comments
Note that the XDG specification uses "should" liberally, and "must" only rarely, so there's very little the XDG specification actually requires things to do in order to be compliant. |
Agreed, but since npm, pnpm and yarn,nvm, ect also provide options for xdg specs, then why not provide an option for corepack as well. People who might want to opt in to xdg specs can use that(like environment variable) |
Is it something you'd like to open a PR for? |
Need to look into this |
came here to open this exact issue. I have XDG user dirs configured and
in my npmrc (location configured via |
* feat: do not use `~/.node` as default value for `COREPACK_HOME` Fixes: #145 Refs: nodejs/node#43859 * fixup! feat: do not use `~/.node` as default value for `COREPACK_HOME` * Update sources/folderUtils.ts Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com> * Update README * migrate old corepack home folder Co-authored-by: Kristoffer K. <merceyz@users.noreply.github.com>
Big thank you to all the guys that worked on this. |
XDG Base Directory
By default, corepack creates folder on
$HOME/.node/corepack
. This should not be the default, but rather a fallback.Default location should be something like
$XDG_CACHE_HOME/node/corepack
or$HOME/.cache/node/corepack
respecting the xdg specificationsThe text was updated successfully, but these errors were encountered: