Fails on Node 7

Question

Fails on Node 7

Closed this issue 6 years ago · 13 comments

I think problem is same as npm/npm#14438

"Same issue with node 7.0.0, downgrade node to 6.9.0 solved that problem."

"I found that to get around that problem I had to:"

Switch Node from 7.0.0 back to 6.x
Then run npm -g install npm@next (or whatever version you want)
Then switch back to Node 7.0.0

> npm-watch

exception in nodemon killing node
Error: Cannot find module 'internal/fs'
    at Function.Module._resolveFilename (module.js:472:15)
    at Function.Module._load (module.js:420:25)
    at Module.require (module.js:500:17)
    at require (internal/module.js:20:19)
    at evalmachine.<anonymous>:17:20
    at Object.<anonymous> (/Users/kristianmandrup/npm/lib/node_modules/nodemon/node_modules/update-notifier/node_modules/configstore/node_modules/graceful-fs/fs.js:11:1)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)

----------------------------------------------------------
If appropriate, please file an error with the output from:
$ /usr/local/bin/node /Users/kristianmandrup/npm/bin/nodemon --ext js,jsx --watch src --watch test --exec npm run test --dump
At http://github.com/remy/nodemon/issues/new
----------------------------------------------------------

Answer 1 · 2016-11-02T15:38:46.000Z

Thank you for pointing this out.
Unfortunately there does not seem to be a better work around as of yet.
I will leave this issue open for a while, although hopefully it will be fixed soon

Answer 2 · 2016-11-02T15:46:47.000Z

Also it should be installed as a global module npm i npm-watch -g, right?
Or perhaps run locally via npm-run?

npm i npm-run npm-quick-run -g

Answer 3 · 2016-11-02T16:02:13.000Z

I usually install locally and then do npm run watch

Answer 4 · 2016-11-29T22:54:06.000Z

@kristianmandrup would it be possible to check if this issue is still occurring for you?

Answer 5 · 2016-11-30T08:42:28.000Z

OK, let me try

Answer 6 · 2016-11-30T08:43:50.000Z

Just installed latest npm-watch globally via npm i -g npm-watch

Node v. 7.1

$ npm-watch
/usr/local/lib/node_modules/npm-watch/watch-package.js:96
    stdin.stderr.write(message)
         ^

TypeError: Cannot read property 'stderr' of undefined
    at die (/usr/local/lib/node_modules/npm-watch/watch-package.js:96:10)
    at watchPackage (/usr/local/lib/node_modules/npm-watch/watch-package.js:16:5)
    at Object.<anonymous> (/usr/local/lib/node_modules/npm-watch/cli.js:12:15)

Answer 7 · 2016-11-30T09:07:48.000Z

yeah....
that definitely should not be happening.
Will look at it later in the day.

two things that would help:

What OS are you on
What is your conifg

Answer 8 · 2016-11-30T09:10:25.000Z

I'm on Mac OS Sierra. What config?

Answer 9 · 2016-11-30T09:12:20.000Z

the watch key in your project,json.

are you just using defaults, or changing settings?

Answer 10 · 2016-11-30T09:43:32.000Z

Oh, I forgot about the watch key. This time I ran the command from a project root with a standard package.json. Should have a better error/warning in that case.

Answer 11 · 2016-11-30T09:45:12.000Z

Very good point. Do you mind opening a new issue to that effect?

Answer 12 · 2017-06-03T09:53:45.000Z

What's the status of the issue? Does this work in node 7+?

Answer 13 · 2019-02-07T19:22:43.000Z

Node 7 has been EOL'ed
And it has been working for me with 8+