-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
npm install fails due to package-lock.json – suggest removal to fix node issues #3430
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
Comments
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you! |
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already. |
Thanks for opening this! I closed the linked pull request you opened for this issue due to the reasons I outlined within its thread. I noticed that this issue was originally opened within the p5.js repository, which is for the p5.js library itself, so I went ahead and transferred it over here to the p5.js editor repo, since it seems more relevant to this project based on your PR. In your steps to reproduce this issue, it seems like you're cloning the p5.js repository by using For working with the p5.js editor, its manual installation instructions suggests to clone your own fork of the p5.js editor by using this command: |
Thanks for the clarification and for transferring the issue to the appropriate repository! You're absolutely right — I mistakenly cloned the p5.js library instead of the ( p5.js-web-editor repo ). I'll go ahead and follow the correct installation steps by cloning my fork of the editor as you suggested ( git clone https://github.com/strtux/p5.js-web-editor.git) and will re-test the steps. I appreciate your guidance and will report back soon with my findings. Thanks again! |
Most appropriate sub-area of p5.js?
p5.js version
Latest from main branch as of April 2025
Web browser and version
Chrome 123.0.6312.107
Operating system
Win 11
Steps to reproduce this
Steps:
git clone https://github.com/processing/p5.js
npm install
in the root directorypackage-lock.json
Expected:
Project dependencies should install cleanly with
npm install
.Actual:
npm install
fails due to mismatched or outdated lockfile dependencies, likely caused bypackage-lock.json
being committed.Suggested Fix:
Consider removing the
package-lock.json
file from the repository to prevent version conflicts during development setup. This will help contributors install dependencies cleanly, especially when Node versions vary.The text was updated successfully, but these errors were encountered: