npm install fails due to package-lock.json – suggest removal to fix node issues

[StrTux]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

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:

1. Clone the repository: git clone https://github.com/processing/p5.js
2. Run npm install in the root directory
3. Observe the node compatibility or package conflict errors due to package-lock.json

Expected:

Project dependencies should install cleanly with npm install.

Actual:

npm install fails due to mismatched or outdated lockfile dependencies, likely caused by package-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.

[welcome]

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]

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.

[raclim]

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 git clone https://github.com/processing/p5.js. This command clones the p5.js library, not the editor.

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: git clone https://github.com/YOUR_USERNAME/p5.js-web-editor.git. Would you be able to give that a try to see if it resolves the issue?

[StrTux]

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!

[raclim]

Since it's been a while I'm going to close this issue for now, but please feel free to reopen this issue or raise a new one if anything comes up!