docs: update module usage instructions to remove Grunt and reflect dev-2.0 tooling #7871

[LalitNarayanYadav]

Changes:

• Removed outdated Grunt-based module bundling instructions from the main "Usage" section.
• Added updated instructions using npm run build for dev-2.0 and guidance on custom builds via Rollup.
• Moved legacy Grunt commands into a clearly labeled section with a deprecation warning.

Fixes #7871

PR Checklist

• npm run lint passes
• Inline reference is included / updated
• Unit tests are included / updated

[ksen0]

Hi @LalitNarayanYadav thanks for working on this! To link the PR to an issue, please write: "Fixes #7871" (if the issue should be closed when this PR is merged; otherwise, write "Addresses [issue]"). Thank you!

[LalitNarayanYadav]

Thanks you @ksen0 ! I'll keep it in mind.

[perminder-17]

These looks good so far, Really thanks for your awesome work. I'll give another round of review. I just need to ask weather you are confirm with these Spanish docs? I'll review them with translating with google translator and AI since I don't know spanish?

[perminder-17]

Yes, these commands look promising, and the npm run lint command appears to work correctly. Could you confirm whether changing the code’s indentation causes the linter to fail, or does it still pass? In my case, it always passes regardless of indentation.

[error-four-o-four]

The linter isn't implemented in v2+ yet. See #7853

In v1+ it wasn't configured for .md files. So my best bet is to not indent the code snippets.

[perminder-17]

Aah...okay. Thanks for letting me know @error-four-o-four :)

[perminder-17]

Hi, I think we should also update the overview section. Currently it's something like:

An excellent new [feature](https://github.com/processing/p5.js/pull/2051) of p5.js allows user to build p5.js as a custom combination of its modules. This greatly helps in reducing the production version size of the library, as well as improves overall performance..

I think, the PR we link here adds a grunt task which takes in the arguments of modules it want to bundle together. Maybe we could remove/update it.

[perminder-17]

This section is meant to show how to create a custom build of p5.js with selected components. Right now, the commands only build the full library and run the test suite. We should remove the final npm test line and replace it with the command that actually generates a custom bundle. I’m not sure whether the dev-2.0 branch already supports modular builds, @limzykenneth , could you confirm if dev-2.0 lets users assemble p5.js from a chosen set of modules, and if so, what the exact command is?

[LalitNarayanYadav]

Thanks for the suggestion, @perminder-17!

You're right , the current commands don't yet support creating a custom p5.js build with selected modules in dev-2.0. As of now, there's no direct equivalent to grunt combineModules in the dev-2.0 tooling.

I've updated the docs to reflect the available npm run build workflow, and removed the npm test line (since it's not relevant to bundling). Once modular builds are supported in dev-2.0, I’d be happy to help update this section with the correct commands.

[perminder-17]

"runs linter and tests using Vitest" also, this line is misleading. Vitest never “runs the linter”, if you look at the script section, we have two different commands,

"scripts" : {
    "test": "vitest",
    "lint": "eslint .",
},

so, for lint we should write npm run lint, however we can probably remove the commands which is used for running tests in p5js from custom_p5_build.md?

[LalitNarayanYadav]

Thanks @perminder-17 for the helpful feedback! I've updated the custom_p5_build.md file to:

• Remove the misleading npm test line
• Clarify that npm run lint is the correct command for linting

Let me know if there's anything else you'd like me to revise.

[LalitNarayanYadav]

Thanks for the review, @perminder-17!

Yes, I did update some Spanish .md files. I verified the changes using both Google Translate and AI-based translation tools to ensure they align with the English versions. However, since I'm not fluent in Spanish, I'd appreciate it if someone with Spanish proficiency could review those sections for accuracy.

Let me know if you’d prefer I flag these specific files for further review.