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
package-json
/package-json/6.5.0: resolution: {integrity: sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ==} engines: {node: '>=8'} dependencies: got: 9.6.0 registry-auth-token: 4.2.2 registry-url: 5.1.0 semver: 6.3.0
I'm happy to open a PR for this @dylang, it appears that the only breaking change for package-json@7 is dropping node 12 support. Is this a problem?
The text was updated successfully, but these errors were encountered:
Looks like this is already updated per:
npm-check/package.json
Line 83 in b9f6666
Has this been released in a separate tag?
Sorry, something went wrong.
+1 here. Are there plans to publish a new version here?
No branches or pull requests
/package-json/6.5.0: resolution: {integrity: sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ==} engines: {node: '>=8'} dependencies: got: 9.6.0 registry-auth-token: 4.2.2 registry-url: 5.1.0 semver: 6.3.0
I'm happy to open a PR for this @dylang, it appears that the only breaking change for package-json@7 is dropping node 12 support. Is this a problem?
The text was updated successfully, but these errors were encountered: