Nuxt 2.9.1 requires an incompatible version of execa
See original GitHub issueA clean install of Nuxt from create-nuxt-app
fails to deploy to now with the following error:
error execa@2.0.4: The engine "node" is incompatible with this module. Expected version "^8.12.0 \|\| >=9.7.0". Got "8.10.0"
The issue is produced by @nuxt/cli
2.9.1 requiring execa 2.0.4 (previously it required 1.0.0).
A work-around for the moment is adding the following to package.json
:
"resolutions": {
"execa": "<=2.0.0"
}
Also note comments to https://github.com/nuxt/now-builder/pull/74.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:6 (2 by maintainers)
Top Results From Across the Web
The engine "node" is incompatible with this module
In my case, I am using yarn workspaces and some of the modules in the package.json files in the workspaces might require foo...
Read more >@nuxtjs/pwa | Yarn - Package Manager
Zero config PWA solution for Nuxt.js. readme. PWA Module. npm version npm downloads Checks Codecov ... See standard-version for commit guidelines.
Read more >Upgrading - Nuxt
Update the version specified for the nuxt package in your package.json file. After this step instructions vary depending upon whether you are using...
Read more >npm fails to install - Google Groups
nThe recommended way to install node is `brew install node`. Node [installed by\nbrew](http://mxcl.github.io/homebrew/) will not require sudo for npm ...
Read more >Third-party software dependencies | Elastic Cloud Enterprise ...
Library Version Optional/Required Packaged
akka‑actor_2.13 2.6.18 Required Yes
akka‑http‑core_2.13 10.2.7 Required Yes
akka‑http‑json4s_2.13 1.27.0 Required Yes
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 reporting!
At ZEIT Now, we already support Node.js 10. it can be selected like this:
Put this into your
package.json
file to select Node.js 10.Also, if your deployment is zero config (no
builds
innow.json
), you will automatically get Node.js 10.Thanks for the workaround!