nodemon: Error with Node v6.0.0?

I just installed Node v6.0.0 and getting a weird error when using nodemon.

> nodemon --exec babel-node ./src/server

(node) v8::ObjectTemplate::Set() with non-primitive values is deprecated
(node) and will stop working in the next major release.

==== JS stack trace =========================================

Security context: 0xddbd16c9fa9 <JS Object>#0#
    1: .node [module.js:568] [pc=0x1ba34b0d4324] (this=0x39c35f3d7b61 <an Object with map 0x3e76c8617be1>#1#,module=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    2: load [module.js:456] [pc=0x1ba34b038e72] (this=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    3: tryModuleLoad(aka tryModuleLoad) [module.js:415] [pc=0x1ba34b03899d] (this=0xddbd1604189 <undefined>,module=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    4: 1: v8::Template::Set(v8::Local<v8::Name>, v8::Local<v8::Data>, v8::PropertyAttribute)
 2: fse::FSEvents::Initialize(v8::Local<v8::Object>)
 3: node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)
 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&))
 5: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>)
 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*)
 7: 0x1ba34af0961b
 8: 0x1ba34b0d4324
(node) v8::ObjectTemplate::Set() with non-primitive values is deprecated
(node) and will stop working in the next major release.

==== JS stack trace =========================================

Security context: 0xddbd16c9fa9 <JS Object>#0#
    1: .node [module.js:568] [pc=0x1ba34b0d4324] (this=0x39c35f3d7b61 <an Object with map 0x3e76c8617be1>#1#,module=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    2: load [module.js:456] [pc=0x1ba34b038e72] (this=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    3: tryModuleLoad(aka tryModuleLoad) [module.js:415] [pc=0x1ba34b03899d] (this=0xddbd1604189 <undefined>,module=0x280a5b1bb8d1 <a Module with map 0x3e76c86181b9>#2#,filename=0x280a5b1bb8a9 <String[111]: /Users/olalonde/code//node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node>)
    4: 1: v8::Template::Set(v8::Local<v8::Name>, v8::Local<v8::Data>, v8::PropertyAttribute)
 2: fse::FSEvents::Initialize(v8::Local<v8::Object>)
 3: node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)
 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&))
 5: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>)
 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*)
 7: 0x1ba34af0961b
 8: 0x1ba34b0d4324
[nodemon] 1.9.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 19
  • Comments: 18 (6 by maintainers)

Commits related to this issue

Most upvoted comments

As a developer, every “+1” hit and leave, discourages me from actually wanting to do anything. It’s the equivalent of saying “yeah! Just fix it!!!” whilst you make no contribution at all.

@remy If no one is in charge of this project then give everyone rights to publish it. https://www.npmjs.com/package/nodemon/access (not me, I’m not interested) Otherwise, if you’re man enough to claim sole ownership of nodemon project then stop crying like a beatch and get things done.

As a developer, every “+1” hit and leave, discourages me from actually wanting to do anything. It’s the equivalent of saying “yeah! Just fix it!!!” whilst you make no contribution at all.

At least olalonde identified that it’s a problem with Chokidar. My guess? Bump the version dep. Send me a PR with a change to the .travis.yml that includes node 6 and I’ll take a look.

+1

+1

Problem seems to be in fsevents library (https://github.com/strongloop/fsevents/issues/127) which is used by chokidar.

All appropriate deps bumped thanks to an external PR and live in 1.9.2. 💟💪

@remy oh man, I feel for you. Sometimes, open source users can feel pretty entitled and forget that you don’t owe them anything. Node v6 was just released and a lot of native modules are breaking due to a backwards incompatible change in the native API (https://github.com/nodejs/node/pull/6277).

I just reported this here as a heads up, best we can do right now is to wait for the upstream modules to get this fixed.

PS: thanks for nodemon!

Yay, guess we can close this now. Just installed nodemon again and error is gone. Added node v6 to travis.yml https://github.com/remy/nodemon/pull/826 if it helps