You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jupyterlab-geojson-extension-0.18.1.tgz
Node v11.13.0
> node /Users/klay6683/miniconda3/envs/py37/lib/python3.7/site-packages/jupyterlab/staging/yarn.js install
yarn install v1.9.4
info No lockfile found.
[1/5] 🔍 Validating package.json...
[2/5] 🔍 Resolving packages...
warning @jupyterlab/application > @jupyterlab/apputils > react > fbjs > [email protected]: core-js@<2.6.5 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
warning css-loader > cssnano > autoprefixer > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning css-loader > cssnano > postcss-merge-rules > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning css-loader > cssnano > postcss-merge-rules > caniuse-api > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[3/5] 🚚 Fetching packages...
[-------------------------------------------------------------------------------------------] 0/836(node:52671) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[4/5] 🔗 Linking dependencies...
warning "@jupyterlab/vdom-extension > @nteract/[email protected]" has incorrect peer dependency "react@^15.6.1".
warning "@jupyterlab/vega4-extension > vega-embed > [email protected]" has unmet peer dependency "vega@*".
[5/5] 📃 Building fresh packages...
success Saved lockfile.
Done in 63.38s.
> node /Users/klay6683/miniconda3/envs/py37/lib/python3.7/site-packages/jupyterlab/staging/yarn.js run build
yarn run v1.9.4
$ webpack
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Ok, next variable is the version of the used npm. Using homebrew's node v11.13.0 for all above tests where it fails. Installing the older node v10.13 from the defaults channel, the install works, and using conda-forge's node 11.11 also works.
michaelaye
changed the title
Same install works on defaults, fails on conda-forge
Install fails with some npm versions for some environment names
Apr 11, 2019
I'm currently have a problem that a previously working standard way of setting up my envs currently fails on the conda-forge site.
Here's a simple complete procedure that works on the defaults channel:
The same done with conda-forge fails for me currently, on the
yarn
end it seems:ends with:
My conda info:
Let me know if I can run the install with some kind of debugging mode to get more info on the failure?
The text was updated successfully, but these errors were encountered: