Support larger range of node versions
See original GitHub issueWas on node 16.3, then upgraded to the latest node (17.2) and both times I got hit by this. Is it possible to lax up on this a little? If you support node 14.15, I’d imagine it would work just fine with everything else?
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-6/auth@1.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-6/core@1.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-6/cloudinary@1.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/button@6.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/core@4.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/fields@6.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/loading@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/notice@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/pill@6.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/icons@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/modals@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/options@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/popover@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/segmented-control@6.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/toast@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@keystone-ui/tooltip@5.0.0',
npm WARN EBADENGINE required: { node: '^14.15 || ^16.13' },
npm WARN EBADENGINE current: { node: 'v17.2.0', npm: '8.1.4' }
npm WARN EBADENGINE }
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Supported Node versions - Node-RED
Node -RED currently recommends Node 16.x LTS. ... We try to stay up to date with Node.js releases. Our goal is to support...
Read more >Node engine 8.x or 10.x in package.json - Stack Overflow
json to accept both 8 and 10 version. I tried to type this: "engines": { "node": "8.x|10.
Read more >Introduction to Version Ranges - Greenkeeper Blog
Version ranges are a measure designed to give you stability. They enable you to, for example, cover patch releases which provide important bug ......
Read more >How To Run Multiple Versions of Node.js with ... - DigitalOcean
Step 1 — Getting Started · Step 2 — Installing Multiple Node.js Versions · Step 3 — Listing Installed Node.js Versions · Step...
Read more >Node Engines: Helping Developers Everywhere Avoid ...
This example includes both a Node version that's greater than or equal to v11.10.2 and less than v12.0.0, and an NPM version of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for resurrecting @AlanBreck! We appreciate community feedback as it helps us know what’s problematic for users 💙
Happy to see it resolved too, thanks! 👍