Comments (5)
That's the expected behaviour. See the documentation:
COREPACK_ENABLE_STRICT
can be set to0
to prevent Corepack from throwing error if the package manager does not correspond to the one defined for the current project. This means that if a user is using the package manager specified in the current project, it will use the version specified by the project'spackageManager
field. But if the user is using other package manager different from the one specified for the current project, it will use the system-wide package manager version.
You can also explicitly call corepack yarn ...
on pnpm projects (or corepack pnpm ...
on Yarn projects) to bypass this check.
from corepack.
Even with no COREPACK_ENABLE_STRICT the error should not happen if pnpm --dir
or yarn --cwd
point to location outside current project.
from corepack.
Corepack has no knowledge of what the underlying package manager CLIs look like, and can only make trivial assumptions about it. If you want a similar behaviour, you'll need to cd
into the target directory and run the command from there.
from corepack.
can only make trivial assumptions about it
Can be trivial if --dir
is on pnpm or --cwd
is on yarn then skip warning.
from corepack.
In my case, the error occurred because I had pnpm in the script that I was trying to run with yarn.
from corepack.
Related Issues (20)
- this[kClient].connect is not a function HOT 6
- Corepack runs into an internal error with newest iron node image [Proxy issue] HOT 4
- Offline workflow does not work HOT 1
- Corepack error with yarn on enable HOT 2
- Silent option on corepack HOT 1
- Frequent fetch() errors HOT 8
- Can't use `pnpm` via corepack when `COREPACK_HOME` is read-only. HOT 4
- feat: store `packageManager` property also inside the lock file HOT 5
- `COREPACK_INTEGRITY_KEYS` being ignored when corepack is spawned by other tools HOT 2
- Could we support corepack enable --yes? HOT 4
- `corepack install --global [email protected]` doesn't work HOT 2
- corepack installs pre-release version of pnpm `9.1.0-0` HOT 1
- CI/CD runs fail: Type Error: URL.canParse is not a function HOT 6
- corepack install verbose error HOT 4
- Corepack doesn't work properly inside official node docker images. HOT 3
- prepare and enable command is not documented HOT 2
- Add quite mode when download file HOT 1
- Metadata retrieval errors when using `COREPACK_NPM_REGISTRY` in combination with Sonatype Nexus
- `prepare` script blocks correct usage HOT 2
- I'll double-check, but the help should be printed on `corepack -h|--help`:
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from corepack.