We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
nodejs/package-maintenance#606
At the moment we use it to manage our pnpm version.
skuba/template/lambda-sqs-worker/Dockerfile
Line 6 in 138129d
skuba/template/lambda-sqs-worker/package.json
Line 41 in 138129d
We probably need to write an autofix of sorts but I'm not entirely sure what the best approach would be right now:
npm i -g corepack && corepack enable?
npm i -g corepack && corepack enable
That would leave us with installing an unpinned corepack version 🤔.
Just leaving a thread here so we aren't surprised when it pops up in the next major node version
The text was updated successfully, but these errors were encountered:
Would it make sense just to install corepack as a dependency in projects? Chicken and egg problem 😢
Sorry, something went wrong.
Might be able to go with something like npm i -g corepack@{version} and have renovate upgrade it?
No branches or pull requests
nodejs/package-maintenance#606
At the moment we use it to manage our pnpm version.
skuba/template/lambda-sqs-worker/Dockerfile
Line 6 in 138129d
skuba/template/lambda-sqs-worker/package.json
Line 41 in 138129d
We probably need to write an autofix of sorts but I'm not entirely sure what the best approach would be right now:
npm i -g corepack && corepack enable
?That would leave us with installing an unpinned corepack version 🤔.
Just leaving a thread here so we aren't surprised when it pops up in the next major node version
The text was updated successfully, but these errors were encountered: