Closed hamhands closed 7 years ago
this is reproducible after blowing away the node_modules
folder and running a fresh npm install
correct?
what version of node? npm?
node --version
npm --version
also, since the problem is that PhantomJS can't be started, can you let me know whether installing the dependencies of Esri Leaflet is what really lays it down or whether the install routine is identifying a previous installation that is accessible via your $PATH
?
Correct.
A previous installation of what specifically?
A previous installation of what specifically?
PhantomJS.
to be honest, our test suite is only relatively stable on Node 4.x and fundamentally broken on 6.x. given that you're currently floating halfway between, i'd recommend rolling back to 4.x if you'd like to set up an environment where you can contribute easily.
i have a hunch we may still have to tackle more issues with your PhantomJS setup afterward, but for now i'll just cross my fingers.
I mean it's not in my path, but the modules are showing up in the project folder.
Rolled back to 4.6.0, got this when I tried to install again:
hamhands:esri-leaflet patr8559$ npm install
> fsevents@1.0.14 install /Users/patr8559/Documents/esri-leaflet/node_modules/fsevents
> node-pre-gyp install --fallback-to-build
[fsevents] Success: "/Users/patr8559/Documents/esri-leaflet/node_modules/fsevents/lib/binding/Release/node-v46-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
> spawn-sync@1.0.15 postinstall /Users/patr8559/Documents/esri-leaflet/node_modules/spawn-sync
> node postinstall
> ws@0.4.32 install /Users/patr8559/Documents/esri-leaflet/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
> esri-leaflet@2.0.3 prepublish /Users/patr8559/Documents/esri-leaflet
> npm run build
> esri-leaflet@2.0.3 prebuild /Users/patr8559/Documents/esri-leaflet
> mkdirp dist
> esri-leaflet@2.0.3 build /Users/patr8559/Documents/esri-leaflet
> rollup -c profiles/debug.js & rollup -c profiles/production.js
npm ERR! Darwin 16.0.0
npm ERR! argv "/Users/patr8559/.nvm/versions/node/v4.6.0/bin/node" "/Users/patr8559/.nvm/versions/node/v4.6.0/bin/npm" "install"
npm ERR! node v4.6.0
npm ERR! npm v2.15.9
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package eslint@1.10.3 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer eslint-config-standard@5.3.1 wants eslint@^2.0.0-rc.0
npm ERR! peerinvalid Peer eslint-config-standard-jsx@1.2.0 wants eslint@^2.0.0-rc.0
npm ERR! Please include the following file with any support request:
npm ERR! /Users/patr8559/Documents/esri-leaflet/npm-debug.log
Ok, nuked the modules, and npm install
ran fine.
npm test returns same error on PhantomJS as above.
two action items
eslint
from package.json dependencies (just to swat away the confusing, irrelevant error) 0286eedis there anything i can help with to confirmPhantomJS is functioning on your machine @hamhands?
@jgravois screenshare? 💻
Found a clue and I think upgrading to "karma-phantomjs-launcher": "^1.0.2"
fixes the issue. PhantomJS launches anyway.
upgrading to
"karma-phantomjs-launcher": "^1.0.2"
fixes the issue.
PR please!
Will do tomorrow! On Wed, Nov 30, 2016 at 7:43 PM john gravois notifications@github.com wrote:
upgrading to "karma-phantomjs-launcher": "^1.0.2" fixes the issue.
PR please!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Esri/esri-leaflet/issues/853#issuecomment-264071016, or mute the thread https://github.com/notifications/unsubscribe-auth/ADeN4HibzwwCris7A633slEX97xzPkHlks5rDkJqgaJpZM4KF_OE .
Steps to reproduce the error:
What happens is: