New release is buggy with Gulp ^3.9.0

[marcelaraujo]

NodeJS 10.0.0
Darwin macbookpro.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jan 11 22:59:40 PST 2018; root:xnu-3789.73.8~1/RELEASE_X86_64 x86_64

⋊> ~/W/I/app on feature/3.20.0 ⨯ ./node_modules/.bin/gulp                                                                                                                                                                                                                        09:26:39
gulp[22423]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const FunctionCallbackInfo<v8::Value> &): Assertion `args[1]->IsString()' failed.
 1: node::Abort() [/usr/local/bin/node]
 2: node::Assert(char const* const (*) [4]) [/usr/local/bin/node]
 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [/usr/local/bin/node]
 5: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<true>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
 6: v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x3f4d75a0427d
 8: 0x3f4d75a0f755
 9: 0x3f4d75a8bc20
10: 0x3f4d75a144f7
11: 0x3f4d75a144f7
fish: './node_modules/.bin/gulp' terminated by signal SIGABRT (Abort)

[devsnek]

yes we changed the internal contextify script to be less lenient with what it accepts. you'll have to update any modules that use it, or better yet find alternatives that don't depend on node internals.

[bnoordhuis]

Duplicate of #20281. (edit: to clarify, same cause if not the exact same module.)

[AyushG3112]

Also see: #19786

[marcelaraujo]

Thanks a lot @AyushG3112 @devsnek and @bnoordhuis

[jperelli]

I updated "grunt-bower-task": "0.4.0", to "grunt-bower-task": "0.5.0", and that fixed it for me, based on the deprecation notice in https://www.npmjs.com/package/natives

[loopmode]

Until a proper fix, this helps:

 "resolutions": {
    "natives": "1.1.3"
  },

[staghouse]

graceful-fs was my particular problem. One of my core dependencies is using it and was installing a version @3 package in my lock file. Adding "graceful-fs": "^4.1.11" in my package.json resolved this issue for me

[netcore-jroger]

I have same problem. Resolved this problem please see issue.

rm -fr node_modules
rm -fr package-lock.json
npm cache clean --force
npm install
// or 
// rm -fr node_modules
// yarn install

[LaudineCOW]

rm -fr node_modules
yarn install

worked for me, but I also had to remove yarn.lock before install.

rm -fr node_modules
rm yarn.lock
yarn install

[zouhairkhallaf]

I just needed to downgrade my node v10.0.0 to a older version

sudo npm cache clean -f
sudo npm install -g n
sudo n 9.0.0

This worked for me

[HawkeyePierce89]

rm -fr package-lock.json

lol

— Hello, my Windows can not boot, can you fix this?
— Yes, no problem (format c:, install Windows from scratch)

[gdky005]

I have same problem. Resolved this problem please see issue.

rm -fr node_modules
rm -fr package-lock.json
npm cache clean --force
npm install
// or 
// rm -fr node_modules
// yarn install

Solves my question.