Comments (12)
zkochan
commented on June 25, 2024
3
Because v8 ignored the packageManager field. v9 uses it by the spec.
from pnpm.
Stanzilla
commented on June 25, 2024
3
Because v8 ignored the packageManager field. v9 uses it by the spec.
is there a chance we can configure this to be less strict? people will often update their package manager (or not) and if they are not using corepack, it won't be done automatically and I don't really want to manually bump the version all the time? Or can it at least work with newer versions? Or only be strict when the patch/major version changes?
from pnpm.
zkochan
commented on June 25, 2024
1
The packageManager field only accepts exact versions. This is invalid: "packageManager": ">[email protected]",
from pnpm.
zkochan
commented on June 25, 2024
1
I don't get it. If you don't want to use the packageManager field by the spec, why don't you just remove it? I don't see how pnpm/action-setup should be changed for this.
from pnpm.
zkochan
commented on June 25, 2024
1
Even if you don't remove it, you can put package-manager-strict=false in .npmrc in the root of your project.
from pnpm.
Ciejo
commented on June 25, 2024
The packageManager field only accepts exact versions. This is invalid:
"packageManager": ">[email protected]",
With version 8.x.x works just fine. I will try putting specific version.
from pnpm.
zkochan
commented on June 25, 2024
If you want something less strict, then use the engines.pnpm field instead, which accepts ranges. The packageManager field is designed like this by the corepack team.
from pnpm.
weyert
commented on June 25, 2024
And breaking changes can be expected from a major version bump.Maybe worth adding to the release notes when it’s missing?Sent from my iPhoneOn 18 Apr 2024, at 01:26, Zoltan Kochan ***@***.***> wrote:
If you want something less strict, then use the engines.pnpm field instead, which accepts ranges. The packageManager field is designed like this by the corepack team.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
from pnpm.
zkochan
commented on June 25, 2024
You can disable this check by setting package-manager-strict to false, or changing the COREPACK_ENABLE_STRICT env varible to 0
from pnpm.
Stanzilla
commented on June 25, 2024
If you want something less strict, then use the engines.pnpm field instead, which accepts ranges. The packageManager field is designed like this by the corepack team.
thanks! looks like that is not suported by https://github.com/pnpm/action-setup/ but I can file a ticket over there
from pnpm.
zkochan
commented on June 25, 2024
Related PR: #7960
from pnpm.
Stanzilla
commented on June 25, 2024
I don't get it. If you don't want to use the packageManager field by the spec, why don't you just remove it? I don't see how pnpm/action-setup should be changed for this.
I was just saying that it would be cool if it also supported the engines.pnpm field
from pnpm.
Related Issues (20)
- "pnpm why" doesn't work properly
- pnpm can create forbidden file name on windows HOT 1
- package peerDependencies are written into the lock file as if they were dependencies. HOT 1
- I cannot update version HOT 3
- `pnpm outdated` is suggesting an *older* version as the latest version
- Can't use pnpm global packages via SSH
- EBUSY: resource busy or locked and EPERM: operation not permitted on windows
- jsonwebtoken package is not compatible
- Missing dev dependencies (or executables) in Dockerfile HOT 1
- add npm "home" command
- The `--cwd` flag is unsupported but does not throw an error
- peerDependenciesMeta.optional ignored after new `pnpm install`
- `package_manager_strict = false` prints warning HOT 1
- node-linker set to pnp and symlink set to false still generated node_modules
- Running install.sh without specifying pnpm version pulls 6.31.0 HOT 6
- Workspace packages peerDependencies don't work HOT 1
- Install fails on OSX HOT 1
- Support `devEngines` field HOT 2
- `pnpm update -r --latest <package-name>` Updates all dependencies instead of only updating the one I selected, (MONOREPO) HOT 4
- `pnpm dedupe` is behaving nondeterministically HOT 4
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 pnpm.