Nuxt.js: console error after upgrading from 2.8.1 to 2.9.1

Created on 20 Aug 2019  Â·  10Comments  Â·  Source: nuxt/nuxt.js

Version

v2.9.1

Reproduction link

https://notavailable.com

Steps to reproduce

npm run dev

and I get

```'find_dp0' is not recognized as an internal or external command,
operable program or batch file.
internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'C:\nuxt\bin\nuxt.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
```

What is expected ?

some help

What is actually happening?

using npm version 6.11 and just upgraded nuxtjs version I got the above error

Additional comments?

I just upgraded from 2.8.1 to 2.9.1 and as soon as
npm run *

  • = dev or build or start

the console drops the error above

This bug report is available on Nuxt community (#c9662)
bug-report

Most helpful comment

@nelsonlarocca Please try to format your posts properly as these are totally unreadable. I guess replying on github emails isnt the best when you add a lot of console output. I tried formatting one post but it didnt work, maybe you can do it.

Thanks :)

All 10 comments

Hi. Please try cleaning node_modules and lock file. That might fix this issue.

Dear Pooya:

Didn’t work out

I’m doing some research now

Just to start

Error: Cannot find module 'C:\nuxt\bin\nuxt.js'

Is not a valid path !

From: Pooya Parsa notifications@github.com
Sent: Tuesday, August 20, 2019 12:02 PM
To: nuxt/nuxt.js nuxt.js@noreply.github.com
Cc: Nelson La Rocca nelson@b4b.net; Author author@noreply.github.com
Subject: Re: [nuxt/nuxt.js] console error after upgrading from 2.8.1 to 2.9.1 (#6259)

Hi. Please try cleaning node_modules and lock file. That might fix this issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, https://github.com/nuxt/nuxt.js/issues/6259?email_source=notifications&email_token=AHF5CBG3547JUZYFTJM2SXLQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q#issuecomment-523151738 view it on GitHub, or https://github.com/notifications/unsubscribe-auth/AHF5CBBRCRL5N4G7KXSQ6NTQFQ5T7ANCNFSM4IN3PWTA mute the thread. https://github.com/notifications/beacon/AHF5CBAN72W3L6S2YPG74VDQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q.gif

Updating

Creating a new app from scratch, lead to a lot of errors !

It seems an environment variable or something like that is not set, node_modules in particular ! since c:\@huxt should be c:\node_modules (for instance)

```

$ npx create-nuxt-app my-app

npx: installed 365 in 74.865s

create-nuxt-app v2.9.2

✨ Generating Nuxt.js project in my-app

? Project name my-app

? Project description Creating a NEW experience for both restaurants and their users

? Author name YaMenu

? Choose the package manager Npm

? Choose UI framework Vuetify.js

? Choose custom server framework None (Recommended)

? Choose Nuxt.js modules Progressive Web App (PWA) Support

? Choose linting tools ESLint, Prettier

? Choose test framework None

? Choose rendering mode Universal (SSR)

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/c

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

 throw err;

 ^

Error: Cannot find module 'C:\@nuxt\opencollective\bin\opencollective.js'

 at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

 at Function.Module._load (internal/modules/cjs/loader.js:562:25)

 at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

 at startup (internal/bootstrap/node.js:283:19)

 at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

 throw err;

 ^

Error: Cannot find module 'C:\@nuxt\opencollective\bin\opencollective.js'

 at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

 at Function.Module._load (internal/modules/cjs/loader.js:562:25)

 at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

 at startup (internal/bootstrap/node.js:283:19)

 at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

npm

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this

npm WARN deprecated package has been deprecated in favor of directly

npm WARN deprecated including core-js/stable (to polyfill ECMAScript

npm WARN deprecated features) and regenerator-runtime/runtime

npm WARN deprecated (needed to use transpiled generator functions):

npm WARN deprecated

npm WARN deprecated > import "core-js/stable";

npm WARN deprecated > import "regenerator-runtime/runtime";

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

 throw err;

 ^

Error: Cannot find module 'C:\@nuxt\opencollective\bin\opencollective.js'

 at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

 at Function.Module._load (internal/modules/cjs/loader.js:562:25)

 at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

 at startup (internal/bootstrap/node.js:283:19)

 at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

npm notice created a lockfile as package-lock.json. You should commit this file.

npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\watchpacknode_modules\fsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

[email protected] install C:\Projects\NUXT\my-appnode_modules\fibers

node build.js || nodejs build.js

win32-x64-64 exists; testing

Binary is fine; exiting

[email protected] lint C:\Projects\NUXT\my-app

eslint --ext .js,.vue --ignore-path .gitignore . "--fix"

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

throw err;

^

Error: Cannot find module 'C:\eslint\bin\eslint.js'

at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

at Function.Module._load (internal/modules/cjs/loader.js:562:25)

at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

at startup (internal/bootstrap/node.js:283:19)

at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

� Successfully created project my-app

To get started:

    cd my-app

    npm run dev

To build & start for production:

    cd my-app

    npm run build

    npm run start

```

From: Pooya Parsa notifications@github.com
Sent: Tuesday, August 20, 2019 12:02 PM
To: nuxt/nuxt.js nuxt.js@noreply.github.com
Cc: Nelson La Rocca nelson@b4b.net; Author author@noreply.github.com
Subject: Re: [nuxt/nuxt.js] console error after upgrading from 2.8.1 to 2.9.1 (#6259)

Hi. Please try cleaning node_modules and lock file. That might fix this issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nuxt/nuxt.js/issues/6259?email_source=notifications&email_token=AHF5CBG3547JUZYFTJM2SXLQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q#issuecomment-523151738 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHF5CBBRCRL5N4G7KXSQ6NTQFQ5T7ANCNFSM4IN3PWTA . https://github.com/notifications/beacon/AHF5CBAN72W3L6S2YPG74VDQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q.gif

Seems an error from your development environment. Are you using cygwin or wsl?

Just got the terminal from git-scm.com

Just for your records, the problem just showed up after the ‘npm update’ updating nuxt

From: Pooya Parsa notifications@github.com
Sent: Tuesday, August 20, 2019 2:53 PM
To: nuxt/nuxt.js nuxt.js@noreply.github.com
Cc: Nelson La Rocca nelson@b4b.net; Author author@noreply.github.com
Subject: Re: [nuxt/nuxt.js] console error after upgrading from 2.8.1 to 2.9.1 (#6259)

Seems an error from your development environment. Are you using cygwin or wsl?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nuxt/nuxt.js/issues/6259?email_source=notifications&email_token=AHF5CBBIOEVDTADAZ6U46JLQFRRVTA5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XYZGQ#issuecomment-523209882 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHF5CBDCN3KQDDE3YRYFSFDQFRRVTANCNFSM4IN3PWTA . https://github.com/notifications/beacon/AHF5CBHC322FMEPCU66N5ZDQFRRVTA5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XYZGQ.gif

Updating !

Tried a new installation in another machine and got right the same:

$ npx create-nuxt-app myapp

npx: installed 365 in 37.61s

create-nuxt-app v2.9.2

✨ Generating Nuxt.js project in myapp

? Project name myapp

? Project description My fantastic Nuxt.js project

? Author name Nelson La Rocca

? Choose the package manager Npm

? Choose UI framework Vuetify.js

? Choose custom server framework None (Recommended)

? Choose Nuxt.js modules Progressive Web App (PWA) Support

? Choose linting tools ESLint, Prettier

? Choose test framework None

? Choose rendering mode Universal (SSR)

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

[email protected] install C:\Projects\NUXT\myappnode_modules\fibers

node build.js || nodejs build.js

win32-x64-64 exists; testing

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

[email protected] install C:\Projects\NUXT\myappnode_modules\fibers

node build.js || nodejs build.js

win32-x64-64 exists; testing

[email protected] install C:\Projects\NUXT\myappnode_modules\fibers

node build.js || nodejs build.js

win32-x64-64 exists; testing

Binary is fine; exiting

[email protected] postinstall C:\Projects\NUXT\myappnode_modules\core-js

npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

 throw err;

 ^

Error: Cannot find module 'C:\@nuxt\opencollective\bin\opencollective.js'

 at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

 at Function.Module._load (internal/modules/cjs/loader.js:562:25)

 at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

 at startup (internal/bootstrap/node.js:283:19)

 at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

npm notice created a lockfile as package-lock.json. You should commit this file.

npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\watchpacknode_modules\fsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

[email protected] install C:\Projects\NUXT\myappnode_modules\fibers

node build.js || nodejs build.js

win32-x64-64 exists; testing

Binary is fine; exiting

[email protected] postinstall C:\Projects\NUXT\myappnode_modules\core-js

[email protected] lint C:\Projects\NUXT\myapp

eslint --ext .js,.vue --ignore-path .gitignore . "--fix"

'find_dp0' is not recognized as an internal or external command,

operable program or batch file.

internal/modules/cjs/loader.js:638

throw err;

^

Error: Cannot find module 'C:\eslint\bin\eslint.js'

at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)

at Function.Module._load (internal/modules/cjs/loader.js:562:25)

at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)

at startup (internal/bootstrap/node.js:283:19)

at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

� Successfully created project myapp

To get started:

    cd myapp

    npm run dev

To build & start for production:

    cd myapp

    npm run build

    npm run start

From: Pooya Parsa notifications@github.com
Sent: Tuesday, August 20, 2019 12:02 PM
To: nuxt/nuxt.js nuxt.js@noreply.github.com
Cc: Nelson La Rocca nelson@b4b.net; Author author@noreply.github.com
Subject: Re: [nuxt/nuxt.js] console error after upgrading from 2.8.1 to 2.9.1 (#6259)

Hi. Please try cleaning node_modules and lock file. That might fix this issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nuxt/nuxt.js/issues/6259?email_source=notifications&email_token=AHF5CBG3547JUZYFTJM2SXLQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q#issuecomment-523151738 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHF5CBBRCRL5N4G7KXSQ6NTQFQ5T7ANCNFSM4IN3PWTA . https://github.com/notifications/beacon/AHF5CBAN72W3L6S2YPG74VDQFQ5T7A5CNFSM4IN3PWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XKS6Q.gif

@nelsonlarocca Please try to format your posts properly as these are totally unreadable. I guess replying on github emails isnt the best when you add a lot of console output. I tried formatting one post but it didnt work, maybe you can do it.

Thanks :)

IMPORTANT UPDATE:

Yesterday I upgraded npm before upgrading nuxt, today a new npm version was available.
This is the only warning I get AFTER upgrading npm to the latest version: 6.11.1

### npm WARN deprecated @babel/[email protected]: � As of Babel 7.4.0, this
npm WARN deprecated package has been deprecated in favor of directly
npm WARN deprecated including core-js/stable (to polyfill ECMAScript
npm WARN deprecated features) and regenerator-runtime/runtime
npm WARN deprecated (needed to use transpiled generator functions):
npm WARN deprecated
npm WARN deprecated   > import "core-js/stable";
npm WARN deprecated   > import "regenerator-runtime/runtime";
npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

Thanks for your contribution to Nuxt.js!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of nuxt-edge
  2. Comment the steps to reproduce it

Issues that are labeled as pending will not be automatically marked as stale.

I'm not sure if I can follow. Please edit your initial post with the correct issue and formatted code if the error persists. Then, ping me or any core team member here and we can reopen the issue

Was this page helpful?
0 / 5 - 0 ratings

Related issues

vadimsg picture vadimsg  Â·  3Comments

mattdharmon picture mattdharmon  Â·  3Comments

bimohxh picture bimohxh  Â·  3Comments

o-alexandrov picture o-alexandrov  Â·  3Comments

vadimsg picture vadimsg  Â·  3Comments