Date: Fri, 1 Dec 2017 15:11:20 -0800 From: Pete Wright <pete@nomadlogic.org> To: freebsd-ports@freebsd.org Subject: Re: Any chance of upgrading www/npm to 5.6.0? Message-ID: <800b4367-3c85-7ec8-7702-732b99894ab6@nomadlogic.org> In-Reply-To: <CAJuc1zNQB9itBxTFRznHhXzp0BhY1JOtEgkru5tmAd2OXwTb-A@mail.gmail.com> References: <CAJuc1zNQB9itBxTFRznHhXzp0BhY1JOtEgkru5tmAd2OXwTb-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/01/2017 14:46, Jonathan Chen wrote: > Hi, > > Currently, with npm-5.4.2_2, I'm getting: > > WARNING: You are likely using a version of node-tar or npm that is > incompatible with this version of Node.js. > Please use either the version of npm that is bundled with Node.js, or > a version of npm (> 5.5.1 or < 5.4.0) or node-tar (> 4.0.1) that is > compatible with Node.js 9 and above. > /usr/local/bin/node[32746]: ../src/node_zlib.cc:437:static void > node::(anonymous namespace)::ZCtx::Init(const > FunctionCallbackInfo<v8::Value> &): Assertion `args.Length() == 7 && > "init(windowBits, level, memLevel, strategy, writeResult, > writeCallback," " dictionary)"' failed. > 1: node::Abort(void) [/usr/local/bin/node] > 2: node::Assert(char const* const[4]*) [/usr/local/bin/node] > 3: _ZNSt3__16vectorIPN4node14SigintWatchdogENS_9allocatorIS3_EEE21__push_back_slow_pathIRKS3_EEvOT_ > [/usr/local/bin/node] > 4: v8::internal::FunctionCallbackArguments::Call(void(*)(v8::FunctionCallbackInfo<v8::Value> > const&)) [/usr/local/bin/node] > 5: v8::internal::Isolate*<v8::internal::Object> > v8::internal::Builtins::InvokeApiFunction(v8::internal::Isolate*, > bool, v8::internal::Handle<v8::internal::HeapObject>(int, > v8::internal::Object*, v8::internal::HeapObject) [/usr/local/bin/node] > 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, > v8::internal::Isolate*) [/usr/local/bin/node] > > It looks like the latest version of npm addresses the incompatibility > between npm & node. Any chance of an upgrade soon? > https://github.com/npm/npm/releases/tag/v5.6.0 hrm i wonder if this would also resolve this PR i filed a little while ago: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223615 -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?800b4367-3c85-7ec8-7702-732b99894ab6>