Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev process: npm i (or npm ci) freezes / takes too long #15813

Closed
2 tasks
xl0 opened this issue Jul 1, 2024 · 5 comments
Closed
2 tasks

Dev process: npm i (or npm ci) freezes / takes too long #15813

xl0 opened this issue Jul 1, 2024 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Issue needs to be triaged user-setup Issues caused by incorrectly configured python environments, packages, or the like

Comments

@xl0
Copy link

xl0 commented Jul 1, 2024

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

I want to hack a bit. Following https://github.com/microsoft/vscode-jupyter/blob/main/CONTRIBUTING.md I ran
npm ci
and it hangs after a while, not showing any progress for over 15 minutes, and not showing up in top.
I see that in CI you use npm ci --ignore-scripts --prefer-offline --no-audit

In my limited experience with node, I've never faced this issue, so not sure if it should be fixed, or the docs should be updated.

(I installed recommended node version through mamba, and then installed the recommended npm version)

VS Code Version

recent

Jupyter Extension Version

master

Jupyter logs

No response

Coding Language and Runtime Version

No response

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Local

@xl0 xl0 added the bug Issue identified by VS Code Team member as probable bug label Jul 1, 2024
@vscodenpa vscodenpa added the triage-needed Issue needs to be triaged label Jul 1, 2024
@xl0
Copy link
Author

xl0 commented Jul 1, 2024

I also had to run
npm run postinstall
To actually get a working environment. But at least it worked. Is this a bug, or just lack of documentation?

@DonJayamanne
Copy link
Contributor

Sorry for never getting back to you. Are you still running into this issue.
We used to have similar issues, however that was related to an npm package that has since been removed.

@DonJayamanne DonJayamanne added the info-needed Issue requires more information from poster label Jul 22, 2024
@xl0
Copy link
Author

xl0 commented Jul 22, 2024

$ npm i
npm WARN deprecated [email protected]: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated @types/[email protected]: This is a stub types definition. del provides its own type definitions, so you do not need this installed.
npm WARN deprecated [email protected]: postinstall-build's behavior is now built into npm! You should migrate off of postinstall-build and use the new `prepare` lifecycle script with npm 5.0.0 or greater.
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: lolex has been renamed to @sinonjs/fake-timers. No API changes made. Please use the new package instead
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: This package has been renamed to @vscode/debugprotocol, please update to the new name
npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated [email protected]: https://about.codecov.io/blog/codecov-uploader-deprecation-plan/
npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
(##################) ⠙ reify:date-fns: timing reifyNode:node_modules/rxjs Completed in 7281ms

(just hangs here, no CPU activity)

@DonJayamanne
Copy link
Contributor

thats so weird, I'm assuming you are using the asme version of node.js 18.15.0?

@xl0
Copy link
Author

xl0 commented Jul 22, 2024

My bad, I had 18, but 18.20 because .15 is broken in mamba.
I downgraded to .17 which is the lowest that can be installed, and now it works!

@DonJayamanne DonJayamanne added the user-setup Issues caused by incorrectly configured python environments, packages, or the like label Jul 22, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Issue needs to be triaged user-setup Issues caused by incorrectly configured python environments, packages, or the like
Projects
None yet
Development

No branches or pull requests

4 participants