corepack
corepack copied to clipboard
nodejs
Zero-runtime-dependency package acting as bridge between Node projects and their package managers
Getting a 403 error ```bash $ nodenv global 17.1.0 $ npm ls -g --depth 0 /home/LOM0227/stow/nodenv/.nodenv/versions/17.1.0/lib ├── [email protected] └── [email protected] $ corepack enable $ pnpm Internal Error: Server answered with...
We were discussing with @iansu the case where package managers are detected depending on whether they are or not in the global path (@ljharb mentioned that as well in another...
## Description I currently have the following `Dockerfile`: ``` FROM node:18-bullseye RUN corepack enable yarn ``` My production environment runs this image in readonly, this way: ``` docker run --rm...
Feature Request: corepack info Running `corepack info` should result in a listing describing what corepack knows about the local directory and how discovered, and then the same information about the...
``` $ corepack prepare yarn@stable --activate Preparing yarn@stable for immediate activation... Internal Error: ENOENT: no such file or directory, stat 'C:\Users\jop\.node\corepack\yarn\3.2.3' Error: ENOENT: no such file or directory, stat 'C:\Users\jop\.node\corepack\yarn\3.2.3'...
`corepack prepare` command with a range of versions behaves differently than expected. ## Case 1 When: - `[email protected]` is the latest published version - no local cache (In OSX, `$HOME/.cache/node/corepack/yarn`...
Corepack on Windows inside of GitHub Actions appears to fail `prepare npm@latest --activate` the first time it is invoked _for some reason_. Subsequent calls to `prepare npm@latest --activate` (appear to)...
I am using yarn 1.22.19 with node 14.19.1 (actually using nvm to be able to use multiple node versions, but I'm not sure this is important here). I assume yarn...
Fixes: https://github.com/nodejs/corepack/issues/379
JSON data is (supposedly) rather innocuous, it seems unnecessary to have a prompt for those. Fixes: https://github.com/nodejs/corepack/issues/380