npm install generates huge list of errors - angularjs
I must preface this question by saying that I am really new to Angular and Node. Following the directions from this Tuts+ tutorial, I cloned a sample Angular repo and then ran npm install. That yielded a massive list of errors, and then left my Terminal hanging for about 5 minutes. After that, I ran npm start and opened the sample app, which seemed to function just fine.
As I said, I'm very new to Angular and Node, so I don't know how to debug the errors I'm seeing, or if it's even something I should worry about. Any insight would be very helpful. Thanks!
npm install log: https://gist.github.com/danielbonnell/30959bd15297f1f4ab43
➜ angular-seed git:(master) npm install
npm WARN engine karma#0.10.10: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.2","npm":"2.7.5"})
npm WARN peerDependencies The peer dependency karma-jasmine#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-requirejs#~0.2.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-coffee-preprocessor#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-html2js-preprocessor#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-chrome-launcher#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-firefox-launcher#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-phantomjs-launcher#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency karma-script-launcher#~0.1.0 included from karma will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
> fsevents#0.2.1 install /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild
CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:6:
../node_modules/nan/nan.h:339:13: error: no member named 'New' in 'v8::String'
return _NAN_ERROR(v8::Exception::Error, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:343:5: error: no member named 'ThrowException' in namespace 'v8'
_NAN_THROW_ERROR(v8::Exception::Error, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
~~~~^
../node_modules/nan/nan.h:343:5: error: no member named 'New' in 'v8::String'
_NAN_THROW_ERROR(v8::Exception::Error, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
^~~~~~~~~~~~~~~~~~~~~~~
macro '_NAN_ERROR'n/nan.h:319:50: note: expanded from -
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:348:9: error: no type named 'ThrowException' in namespace 'v8'
v8::ThrowException(error);
~~~~^
../node_modules/nan/nan.h:355:65: error: no member named 'New' in 'v8::String'
v8::Local<v8::Value> err = v8::Exception::Error(v8::String::New(msg));
~~~~~~~~~~~~^
../node_modules/nan/nan.h:357:26: error: no member named 'New' in 'v8::String'
obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber));
~~~~~~~~~~~~^
../node_modules/nan/nan.h:357:65: error: too few arguments to function call, expected 2, have 1
obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber));
~~~~~~~~~~~~~~ ^
/Users/ACIDSTEALTH/.node-gyp/0.12.2/deps/v8/include/v8.h:2012:3: note: 'New' declared here
static Local<Integer> New(Isolate* isolate, int32_t value);
^
In file included from ../fsevents.cc:6:
../node_modules/nan/nan.h:369:12: error: no member named 'New' in 'v8::String'
return _NAN_ERROR(v8::Exception::TypeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:373:5: error: no member named 'ThrowException' in namespace 'v8'
_NAN_THROW_ERROR(v8::Exception::TypeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
~~~~^
../node_modules/nan/nan.h:373:5: error: no member named 'New' in 'v8::String'
_NAN_THROW_ERROR(v8::Exception::TypeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
^~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:377:12: error: no member named 'New' in 'v8::String'
return _NAN_ERROR(v8::Exception::RangeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:381:5: error: no member named 'ThrowException' in namespace 'v8'
_NAN_THROW_ERROR(v8::Exception::RangeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
~~~~^
../node_modules/nan/nan.h:381:5: error: no member named 'New' in 'v8::String'
_NAN_THROW_ERROR(v8::Exception::RangeError, errmsg);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR'
v8::ThrowException(_NAN_ERROR(fun, errmsg)); \
^~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR'
# define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg))
~~~~~~~~~~~~^
../node_modules/nan/nan.h:727:49: error: too few arguments to function call, single argument 'isolate' was not specified
v8::Local<v8::Object> obj = v8::Object::New();
~~~~~~~~~~~~~~~ ^
/Users/ACIDSTEALTH/.node-gyp/0.12.2/deps/v8/include/v8.h:2388:3: note: 'New' declared here
static Local<Object> New(Isolate* isolate);
^
In file included from ../fsevents.cc:6:
../node_modules/nan/nan.h:733:49: error: too few arguments to function call, single argument 'isolate' was not specified
v8::Local<v8::Object> obj = v8::Object::New();
~~~~~~~~~~~~~~~ ^
/Users/ACIDSTEALTH/.node-gyp/0.12.2/deps/v8/include/v8.h:2388:3: note: 'New' declared here
static Local<Object> New(Isolate* isolate);
^
In file included from ../fsevents.cc:6:
../node_modules/nan/nan.h:740:12: error: no member named 'Dispose' in 'v8::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >'
handle.Dispose();
~~~~~~ ^
../node_modules/nan/nan.h:741:12: error: no member named 'Clear' in 'v8::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object> >'
handle.Clear();
~~~~~~ ^
../node_modules/nan/nan.h:746:39: error: no member named 'NewSymbol' in 'v8::String'; did you mean 'IsSymbol'?
NanPersistentToLocal(handle)->Set(NanSymbol("callback"), fn);
^~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:181:38: note: expanded from macro 'NanSymbol'
#define NanSymbol(value) v8::String::NewSymbol(value)
~~~~~~~~~~~~^
/Users/ACIDSTEALTH/.node-gyp/0.12.2/deps/v8/include/v8.h:1379:8: note: 'IsSymbol' declared here
bool IsSymbol() const;
^
In file included from ../fsevents.cc:6:
../node_modules/nan/nan.h:746:39: error: call to non-static member function without an object argument
NanPersistentToLocal(handle)->Set(NanSymbol("callback"), fn);
^~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:181:38: note: expanded from macro 'NanSymbol'
#define NanSymbol(value) v8::String::NewSymbol(value)
~~~~~~~~~~~~^~~~~~~~~
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.3.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma/node_modules/chokidar/node_modules/fsevents
gyp ERR! node -v v0.12.2
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm WARN optional dep failed, continuing fsevents#0.2.1
> ws#0.4.32 install /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/bufferutil.node
SOLINK_MODULE(target) Release/bufferutil.node: Finished
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
SOLINK_MODULE(target) Release/validation.node: Finished
npm WARN peerDependencies The peer dependency requirejs#~2.1 included from karma-requirejs will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
\
> phantomjs#1.9.16 install /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma-phantomjs-launcher/node_modules/phantomjs
> node install.js
PhantomJS detected, but wrong version 2.0.0 # /usr/local/bin/phantomjs.
Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-macosx.zip
Saving to /var/folders/bq/g95dzyzn6nv074fpfhz2tjkh0000gn/T/phantomjs/phantomjs-1.9.8-macosx.zip
Receiving...
[========================----------------] 60% 0.0s
Received 9187K total.
Extracting zip contents
Removing /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma-phantomjs-launcher/node_modules/phantomjs/lib/phantom
Copying extracted folder /var/folders/bq/g95dzyzn6nv074fpfhz2tjkh0000gn/T/phantomjs/phantomjs-1.9.8-macosx.zip-extract-1429227494807/phantomjs-1.9.8-macosx -> /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma-phantomjs-launcher/node_modules/phantomjs/lib/phantom
Writing location.js file
Done. Phantomjs binary available at /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed/node_modules/karma-phantomjs-launcher/node_modules/phantomjs/lib/phantom/bin/phantomjs
> angular-seed#0.0.0 postinstall /Users/ACIDSTEALTH/Dropbox/Launch_Academy/angular-seed
> bower install
bower html5-boilerplate#~4.3.0 not-cached git://github.com/h5bp/html5-boilerplate.git#~4.3.0
bower html5-boilerplate#~4.3.0 resolve git://github.com/h5bp/html5-boilerplate.git#~4.3.0
bower angular-route#1.2.x not-cached git://github.com/angular/bower-angular-route.git#1.2.x
bower angular-route#1.2.x resolve git://github.com/angular/bower-angular-route.git#1.2.x
bower angular-loader#1.2.x not-cached git://github.com/angular/bower-angular-loader.git#1.2.x
bower angular-loader#1.2.x resolve git://github.com/angular/bower-angular-loader.git#1.2.x
bower angular-mocks#~1.2.x not-cached git://github.com/angular/bower-angular-mocks.git#~1.2.x
bower angular-mocks#~1.2.x resolve git://github.com/angular/bower-angular-mocks.git#~1.2.x
bower angular#1.2.x not-cached git://github.com/angular/bower-angular.git#1.2.x
bower angular#1.2.x resolve git://github.com/angular/bower-angular.git#1.2.x
bower html5-boilerplate#~4.3.0 download https://github.com/h5bp/html5-boilerplate/archive/v4.3.0.tar.gz
bower angular-mocks#~1.2.x download https://github.com/angular/bower-angular-mocks/archive/v1.2.28.tar.gz
bower angular#1.2.x download https://github.com/angular/bower-angular/archive/v1.2.28.tar.gz
bower angular-route#1.2.x download https://github.com/angular/bower-angular-route/archive/v1.2.28.tar.gz
bower angular-loader#1.2.x download https://github.com/angular/bower-angular-loader/archive/v1.2.28.tar.gz
bower html5-boilerplate#~4.3.0 extract archive.tar.gz
bower angular-mocks#~1.2.x extract archive.tar.gz
bower angular-loader#1.2.x extract archive.tar.gz
bower angular-route#1.2.x extract archive.tar.gz
bower angular-mocks#~1.2.x resolved git://github.com/angular/bower-angular-mocks.git#1.2.28
bower angular#1.2.x extract archive.tar.gz
bower angular-loader#1.2.x resolved git://github.com/angular/bower-angular-loader.git#1.2.28
bower angular-route#1.2.x resolved git://github.com/angular/bower-angular-route.git#1.2.28
bower angular#1.2.x resolved git://github.com/angular/bower-angular.git#1.2.28
bower html5-boilerplate#~4.3.0 invalid-meta html5-boilerplate is missing "main" entry in bower.json
bower html5-boilerplate#~4.3.0 invalid-meta html5-boilerplate is missing "ignore" entry in bower.json
bower html5-boilerplate#~4.3.0 resolved git://github.com/h5bp/html5-boilerplate.git#4.3.0
bower angular-mocks#~1.2.x install angular-mocks#1.2.28
bower angular-loader#1.2.x install angular-loader#1.2.28
bower angular-route#1.2.x install angular-route#1.2.28
bower angular#1.2.x install angular#1.2.28
bower html5-boilerplate#~4.3.0 install html5-boilerplate#4.3.0
angular-mocks#1.2.28 app/bower_components/angular-mocks
└── angular#1.2.28
angular-loader#1.2.28 app/bower_components/angular-loader
└── angular#1.2.28
angular-route#1.2.28 app/bower_components/angular-route
└── angular#1.2.28
angular#1.2.28 app/bower_components/angular
html5-boilerplate#4.3.0 app/bower_components/html5-boilerplate
karma-junit-reporter#0.2.2 node_modules/karma-junit-reporter
└── xmlbuilder#0.4.2
shelljs#0.2.6 node_modules/shelljs
http-server#0.6.1 node_modules/http-server
├── opener#1.3.0
├── colors#0.6.2
├── portfinder#0.2.1 (mkdirp#0.0.7)
├── optimist#0.5.2 (wordwrap#0.0.2)
├── ecstatic#0.4.13 (ent#0.0.7, mime#1.2.11, optimist#0.3.7)
└── union#0.3.8 (pkginfo#0.2.3, qs#0.5.6)
protractor#1.8.0 node_modules/protractor
├── jasminewd#1.1.0
├── jasminewd2#0.0.2
├── saucelabs#0.1.1
├── html-entities#1.1.2
├── q#1.0.0
├── minijasminenode#1.1.1
├── adm-zip#0.4.4
├── optimist#0.6.1 (wordwrap#0.0.2, minimist#0.0.10)
├── source-map-support#0.2.10 (source-map#0.1.32)
├── glob#3.2.11 (inherits#2.0.1, minimatch#0.3.0)
├── accessibility-developer-tools#2.6.0
├── lodash#2.4.1
├── request#2.36.0 (aws-sign2#0.5.0, forever-agent#0.5.2, json-stringify-safe#5.0.0, qs#0.6.6, tunnel-agent#0.4.0, oauth-sign#0.3.0, mime#1.2.11, node-uuid#1.4.3, tough-cookie#0.12.1, form-data#0.1.4, http-signature#0.10.1, hawk#1.0.0)
├── jasmine#2.1.1 (jasmine-core#2.1.3)
└── selenium-webdriver#2.44.0 (tmp#0.0.24, xml2js#0.4.4)
bower#1.4.1 node_modules/bower
├── is-root#1.0.0
├── junk#1.0.1
├── stringify-object#1.0.1
├── abbrev#1.0.5
├── user-home#1.1.1
├── chmodr#0.1.0
├── which#1.0.9
├── rimraf#2.3.2
├── archy#1.0.0
├── opn#1.0.1
├── bower-logger#0.2.2
├── bower-endpoint-parser#0.2.2
├── graceful-fs#3.0.6
├── lockfile#1.0.0
├── lru-cache#2.6.1
├── nopt#3.0.1
├── retry#0.6.1
├── tmp#0.0.24
├── q#1.2.0
├── request-progress#0.3.1 (throttleit#0.0.2)
├── shell-quote#1.4.3 (array-filter#0.0.1, array-map#0.0.0, array-reduce#0.0.0, jsonify#0.0.0)
├── chalk#1.0.0 (escape-string-regexp#1.0.3, ansi-styles#2.0.1, supports-color#1.3.1, strip-ansi#2.0.1, has-ansi#1.0.3)
├── bower-json#0.4.0 (intersect#0.0.3, deep-extend#0.2.11, graceful-fs#2.0.3)
├── semver#2.3.2
├── fstream#1.0.4 (inherits#2.0.1)
├── p-throttler#0.1.1 (q#0.9.7)
├── promptly#0.2.0 (read#1.0.5)
├── mkdirp#0.5.0 (minimist#0.0.8)
├── tar-fs#1.5.0 (pump#1.0.0, tar-stream#1.1.3)
├── fstream-ignore#1.0.2 (inherits#2.0.1, minimatch#2.0.4)
├── glob#4.5.3 (inherits#2.0.1, inflight#1.0.4, once#1.3.1, minimatch#2.0.4)
├── insight#0.5.3 (object-assign#2.0.0, lodash.debounce#3.0.3, async#0.9.0, os-name#1.0.3, tough-cookie#0.12.1)
├── update-notifier#0.3.2 (is-npm#1.0.0, string-length#1.0.0, semver-diff#2.0.0, latest-version#1.0.0)
├── decompress-zip#0.1.0 (mkpath#0.1.0, touch#0.0.3, readable-stream#1.1.13, binary#0.3.0)
├── github#0.2.3
├── bower-registry-client#0.3.0 (graceful-fs#2.0.3, request-replay#0.2.0, rimraf#2.2.8, lru-cache#2.3.1, async#0.2.10, mkdirp#0.3.5, request#2.51.0)
├── cardinal#0.4.4 (ansicolors#0.2.1, redeyed#0.4.4)
├── request#2.53.0 (caseless#0.9.0, json-stringify-safe#5.0.0, forever-agent#0.5.2, aws-sign2#0.5.0, stringstream#0.0.4, oauth-sign#0.6.0, tunnel-agent#0.4.0, isstream#0.1.2, qs#2.3.3, node-uuid#1.4.3, combined-stream#0.0.7, form-data#0.2.0, mime-types#2.0.10, bl#0.9.4, http-signature#0.10.1, tough-cookie#0.12.1, hawk#2.3.1)
├── bower-config#0.6.1 (osenv#0.0.3, graceful-fs#2.0.3, optimist#0.6.1, mout#0.9.1)
├── mout#0.11.0
├── handlebars#2.0.0 (optimist#0.3.7, uglify-js#2.3.6)
├── configstore#0.3.2 (object-assign#2.0.0, xdg-basedir#1.0.1, osenv#0.1.0, uuid#2.0.1, js-yaml#3.2.7)
└── inquirer#0.8.0 (figures#1.3.5, ansi-regex#1.1.1, mute-stream#0.0.4, through#2.3.7, readline2#0.1.1, lodash#2.4.1, rx#2.5.2, cli-color#0.3.3, chalk#0.5.1)
karma-firefox-launcher#0.1.4 node_modules/karma-firefox-launcher
karma-script-launcher#0.1.0 node_modules/karma-script-launcher
karma-html2js-preprocessor#0.1.0 node_modules/karma-html2js-preprocessor
karma-jasmine#0.1.5 node_modules/karma-jasmine
karma-chrome-launcher#0.1.8 node_modules/karma-chrome-launcher
└── which#1.0.9
requirejs#2.1.17 node_modules/requirejs
karma-requirejs#0.2.2 node_modules/karma-requirejs
karma-coffee-preprocessor#0.1.3 node_modules/karma-coffee-preprocessor
└── coffee-script#1.7.1 (mkdirp#0.3.5)
karma-phantomjs-launcher#0.1.4 node_modules/karma-phantomjs-launcher
└── phantomjs#1.9.16 (which#1.0.9, progress#1.1.8, kew#0.4.0, request-progress#0.3.1, adm-zip#0.4.4, npmconf#2.1.1, request#2.42.0, fs-extra#0.16.5)
karma#0.10.10 node_modules/karma
├── di#0.0.1
├── graceful-fs#1.2.3
├── colors#0.6.0-1
├── rimraf#2.1.4
├── mime#1.2.11
├── q#0.9.7
├── glob#3.1.21 (inherits#1.0.0)
├── minimatch#0.2.14 (sigmund#1.0.0, lru-cache#2.6.1)
├── optimist#0.3.7 (wordwrap#0.0.2)
├── coffee-script#1.6.3
├── lodash#1.1.1
├── log4js#0.6.23 (async#0.2.10, underscore#1.8.2, readable-stream#1.0.33, semver#4.3.3)
├── http-proxy#0.10.4 (colors#0.6.2, pkginfo#0.3.0, optimist#0.6.1, utile#0.2.1)
├── chokidar#0.8.4 (recursive-readdir#0.0.2)
├── connect#2.8.8 (methods#0.0.1, uid2#0.0.2, pause#0.0.1, cookie-signature#1.0.1, qs#0.6.5, fresh#0.2.0, bytes#0.2.0, buffer-crc32#0.2.1, cookie#0.1.0, send#0.1.4, debug#2.1.3, formidable#1.0.14)
├── useragent#2.0.10 (lru-cache#2.2.4)
└── socket.io#0.9.17 (base64id#0.1.0, policyfile#0.0.4, redis#0.7.3, socket.io-client#0.9.16)
Karma 0.10 incompatible with node 0.12
npm WARN engine karma#0.10.10: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.2","npm":"2.7.5"})
Switch to a node 0.10 version and the install will probably work.
If I understand your question correctly, the reason why got the errors is that your Node.js version does not match with Angular.js
karma#0.10.10: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.2","npm":"2.7.5"})
there is two way to fix your problem
Downgrade your Node.js version to match with Angular.js
Install nvm to switch your Node.js version
but i suggest you try the latter as it is an easy way to manage Node.js version using the nvm.
wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.2","npm":"2.7.5"})
As per message, you need to to downgrade your node package, since the package is not compatible with the newest node. This can be achieved by the following commands:
npm install -g n
n 0.10.44
node --version
The n package interactively manages all your node versions.
To switch back to the latest, run: n latest.
Related
Is there a way to solve any jest package issues?
I have a react.js project and have just gotten started with testing. I installed the react-testing-library and jest to get started with it.
However, when I run
npm test
I get the following error.
/Users/Tomascdmota/Downloads/Trust-Motores-main/node_modules/react-scripts/node_modules/jest-cli/build/cli/index.js:40
execute(argv, argv.projects, result => {
^
TypeError: execute is not a function
at Object.run (/Users/Tomascdmota/Downloads/Trust-Motores-main/node_modules/react-scripts/node_modules/jest-cli/build/cli/index.js:40:3)
at Object.<anonymous> (/Users/Tomascdmota/Downloads/Trust-Motores-main/node_modules/react-scripts/scripts/test.js:104:6)
at Module._compile (node:internal/modules/cjs/loader:1091:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1120:10)
at Module.load (node:internal/modules/cjs/loader:971:32)
at Function.Module._load (node:internal/modules/cjs/loader:812:14)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
at node:internal/main/run_main_module:17:47
My jest version is 26.6.0
I haven't added anything.
I have deleted the node_modules, package-lock.json, yarn.lock and removed jest from the dependencies/DevDependencies. After that I ran yarn install.
I still get that same error. I have googled the error and looked it up here on SO but came short-handed.
Any helps is appreciated.
I have deleted the node_modules, package-lock.json, yarn.lock If you had package-lock.json and yarn.lock files at the same time, it looks like at some point you probably used both yarn and npm to install packages, which can definitely cause conflicts. In terms of this specific issue, I ran into the exact same problem and it was due to a package conflict with jest-cli. The solution in my case was to upgrade react-scripts, e.g. (pick one): Yarn yarn add react-scripts Or NPM npm i react-scripts#latest Details In case it helps, here are more details on my specific issue and how I resolved it. I got the same error and it looks like I had two different versions of jest-cli installed: $ npm list jest-cli ├─┬ jest-enzyme#4.2.0 │ └─┬ jest#27.5.1 │ └── jest-cli#27.5.1 └─┬ react-scripts#1.1.0 └─┬ jest#20.0.4 └── jest-cli#20.0.4 In my case, the solution was to upgrade react-scripts: npm i react-scripts#latest It looks like the dependency conflict is now resolved: $ npm list jest-cli └─┬ jest-enzyme#4.1.1 └─┬ jest#27.5.1 └── jest-cli#27.5.1 In fact, it doesn't even show jest-cli as a dependency of react-scripts any more, because it's using the same version of jest as jest-enzyme now: $ npm list jest ├─┬ jest-enzyme#4.1.1 │ └── jest#27.5.1 └─┬ react-scripts#5.0.0 ├─┬ jest-watch-typeahead#1.0.0 │ └── jest#27.5.1 deduped └── jest#27.5.1 deduped
No package.json file on NPM start
I'm getting back this error when I try NPM start on windows after creating a react file. $ npm start npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Users\Ronan\desktop\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\Ronan\desktop\package.json' Edit: Heres a pic of my file tree if that helps.
To get a react project running, you would have to use a tool called the Node Package Execute "npx" to kickstart a create-react-app project, see illustration below: npx create-react-app your-app-name Doing this will generate a small react project with all the directories/files you need to start building your react app, The directory you should get will look like the below: your-app-name ├── README.md ├── node_modules ├── package.json ├── .gitignore ├── public │ ├── favicon.ico │ ├── index.html │ └── manifest.json └── src ├── App.css ├── App.js ├── App.test.js ├── index.css ├── index.js ├── logo.svg └── serviceWorker.js └── setupTests.js running npm start inside this directory should kickstart a localhost:3000 server where you can see a preview of your project in your browser.
Module not found: Can't resolve 'watson-react-components'
I try to run a REACT application on bluemix / IBMCloud which runs successful on my local workstation.
I get the error Module not found: Can't resolve 'watson-react-components'
when I invoke the application (deploy to bluemix is successful)
Here the import statement im my java script code
import React from 'react';
import './Conversation.css';
import { InputWithButton } from 'watson-react-components';
import Message from './Message.js';
I install the packagethe following install commands
# Install & build
npm install && npm install watson-react-components && npm run build
this is what I get during the installation of the packages
│ └── whatwg-fetch#2.0.3
└─┬ watson-react-components#0.6.16
├── map-range#0.1.2
├── numeral#2.0.6
├─┬ prismjs#1.11.0
│ └─┬ clipboard#1.7.1
│ ├─┬ good-listener#1.2.2
│ │ └── delegate#3.2.0
│ ├── select#1.1.2
│ └── tiny-emitter#2.0.2
Here the error message on the app
Failed to compile
./src/Conversation.js
Module not found: Can't resolve 'watson-react-components' in '/home/vcap/app/src'
sorry sorry --- the problem was sitting in front of the computer. I missed the cf push command in the deployment script. Problem solved!!! sorry again
The bug is in the command to install the app. It should be npm install && npm install --save watson-react-components && npm run build You forgot a --save
NPM transitive dependencies do not work for Angular [duplicate]
For example, when I install Angular2: npm install --save angular2 temp#1.0.0 /Users/doug/Projects/dougludlow/temp ├── angular2#2.0.0-beta.3 ├── UNMET PEER DEPENDENCY es6-promise#^3.0.2 ├── UNMET PEER DEPENDENCY es6-shim#^0.33.3 ├── UNMET PEER DEPENDENCY reflect-metadata#0.1.2 ├── UNMET PEER DEPENDENCY rxjs#5.0.0-beta.0 └── UNMET PEER DEPENDENCY zone.js#0.5.11 npm WARN angular2#2.0.0-beta.3 requires a peer of es6-promise#^3.0.2 but none was installed. npm WARN angular2#2.0.0-beta.3 requires a peer of es6-shim#^0.33.3 but none was installed. npm WARN angular2#2.0.0-beta.3 requires a peer of reflect-metadata#0.1.2 but none was installed. npm WARN angular2#2.0.0-beta.3 requires a peer of rxjs#5.0.0-beta.0 but none was installed. npm WARN angular2#2.0.0-beta.3 requires a peer of zone.js#0.5.11 but none was installed. Is there a magic flag that I can pass to npm that will install the peer dependencies as well? I haven't been able to find one... It's tedious to manually copy and paste the peer dependencies and make sure I have the correct versions. In other words, I'd rather not have to do: npm install --save angular2#2.0.0-beta.3 es6-promise#^3.0.2 es6-shim#^0.33.3 reflect-metadata#0.1.2 rxjs#5.0.0-beta.0 zone.js#0.5.11 What is the better way?
npm version 7 and newer npm v7 has reintroduced the automatic peerDependencies installation. Now in V7, as in versions before V3, you only need to do an npm i and all peerDependences should be automatically installed. They had made some changes to fix old problems as version compatibility across multiple dependants. You can see the discussion and the announcement. Older Answer The automatic install of peer dependencies was explicitly removed with npm 3, as it cause more problems than it tried to solve. You can read about it here for example: https://blog.npmjs.org/post/110924823920/npm-weekly-5 https://github.com/npm/npm/releases/tag/v3.0.0 So no, for the reasons given, you cannot install them automatically with npm 3 upwards.
I solved it by rewriting package.json with the exact values warnings were about. Warnings when running npm: npm WARN angular2#2.0.0-beta.3 requires a peer of es6-shim#^0.33.3 but none was installed. npm WARN angular2#2.0.0-beta.3 requires a peer of reflect-metadata#0.1.2 In package.json, write "es6-shim": "^0.33.3", "reflect-metadata": "0.1.2", Then, delete node_modules directory. Finally, run the command below: npm install
Cheat code helpful in this scenario and some others... ├── UNMET PEER DEPENDENCY #angular/common#4.0.2 ├── UNMET PEER DEPENDENCY #angular/compiler#4.0.2 ├── UNMET PEER DEPENDENCY #angular/compiler-cli#4.0.2 ├── UNMET PEER DEPENDENCY #angular/core#4.0.2 ├── UNMET PEER DEPENDENCY #angular/forms#4.0.2 ├── UNMET PEER DEPENDENCY #angular/http#4.0.2 ├── UNMET PEER DEPENDENCY #angular/platform-browser#4.0.2 ├── UNMET PEER DEPENDENCY #angular/platform-browser-dynamic#4.0.2 > copy & paste your error into your code editor. Highlight an unwanted part with your curser. In this case ├── UNMET PEER DEPENDENCY Press command + d a bunch of times. Press delete twice. (Press space if you accidentally highlighted ├── UNMET PEER DEPENDENCY ) Press up once. Add npm install Press down once. Add --save Copy your stuff back into the cli and run npm install #angular/common#4.0.2 #angular/compiler#4.0.2 #angular/compiler-cli#4.0.2 #angular/core#4.0.2 #angular/forms#4.0.2 #angular/http#4.0.2 #angular/platform-browser#4.0.2 #angular/platform-browser-dynamic#4.0.2 --save
I experienced these errors when I was developing an npm package that had peerDependencies. I had to ensure that any peerDependencies were also listed as devDependencies. The project would not automatically use the globally installed packages.
The project npm-install-peers will detect peers and install them. As of v1.0.1 it doesn't support writing back to the package.json automatically, which would essentially solve our need here. Please add your support to issue in flight: https://github.com/spatie/npm-install-peers/issues/4
I was facing the same issue, lucky I found an alternative way to install peer dependencies along with the install command.
Step 1: $ npm i npm-install-peers -D
for more clarity about the plugin: https://www.npmjs.com/package/npm-install-peers
Step 2: Update package.json for magical script
....
"scripts": {
...
"postinstall": "npm-install-peers"
},
....
Step 3: Just need to hit the install command to get installed all plugins
$ npm install
Install yarn and then run: yarn global add install-peerdeps
react-router peerDependencies error
I'm trying to install react-router but I get the following error. $ npm install react-router npm WARN peerDependencies The peer dependency react#0.13.x included from react-router will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. npm ERR! Windows_NT 6.3.9600 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "react-router" npm ERR! node v0.12.7 npm ERR! npm v2.11.3 npm ERR! code EPEERINVALID npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer react-addons-test-utils#0.14.0-rc1 wants react#^0.14.0-rc1 npm ERR! peerinvalid Peer react-router#0.13.4 wants react#0.13.x npm ERR! peerinvalid Peer react-bootstrap#0.25.2 wants react#>=0.13 npm ERR! Please include the following file with any support request: npm ERR! C:\ReactApps\good start\npm-debug.log The package.json for react in node-modules shows that I use: "version": "0.14.0-rc1", Should I install an earlier version? It seems that 0.13.x might be a better supported version? If that is the case, how can I install without messing up my current project? After using npm install npm -g I typed npm -v and saw that the version in my project is still 2.11.13. I figured that it might be a local version of NPM so I typed: npm install npm hoping to get the latest version updated locally, but still got 2.11.13 when I checked for the version. comp-asus XXX64 /c/ReactApps/goodRouter/goodrouter (master) $ npm -v 2.11.3 comp-asus XXX64 /c/ReactApps/goodRouter/goodrouter (master) $ npm install react-router npm WARN peerDependencies The peer dependency react#0.13.x included from react-router will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. npm ERR! Windows_NT 6.3.9600 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "react-router" npm ERR! node v0.12.7 npm ERR! npm v2.11.3 npm ERR! code EPEERINVALID npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer react-router#0.13.4 wants react#0.13.x npm ERR! Please include the following file with any support request: npm ERR! C:\ReactApps\goodRouter\goodrouter\npm-debug.log When checking globally I can see that it is updated: $ npm list -g --depth=0 C:\Users\Roger\AppData\Roaming\npm ├── babel-eslint#4.1.3 ├── bower#1.5.2 ├── eslint#1.5.1 ├── findup-sync#0.2.1 ├── generator-angular#0.12.1 ├── generator-karma#1.0.0 ├── generator-meanjs#0.1.12 ├── generator-polymer#1.1.0 ├── generator-react-boilerplate#0.1.9 ├── generator-react-webpack#1.2.12 ├── grunt-cli#0.1.13 ├── gulp#3.9.0 ├── httpster#1.0.1 ├── jspm#0.16.10 ├── jsxhint#0.15.1 ├── live-server#0.8.1 ├── mean-cli#0.10.14 ├── mocha#2.2.5 ├── node-gyp#2.0.2 ├── npm#3.3.5 ├── react-tools#0.13.3 ├── superstatic#2.2.1 ├── tsd#0.6.4 ├── typescript#1.7.0-dev.20150921 invalid ├── webpack#1.12.2 └── yo#1.4.7 But how do I use the global version in the project? So the problem persists but I do believe you put me on the right track. $ where npm C:\Program Files\nodejs\npm C:\Program Files\nodejs\npm.cmd C:\Users\Roger\AppData\Roaming\npm\npm C:\Users\Roger\AppData\Roaming\npm\npm.cmd So I should delete one of these?
This is one of the major issues solved in npm#3. See https://github.com/npm/npm/issues/6565 for details. Updating npm is the right thing to do: $ npm install npm -g