X Tutup
Skip to content

feat: added the logic for generating reference docs from local custom build of p5.sound.js#1223

Open
kunstewi wants to merge 2 commits intoprocessing:2.0from
kunstewi:2.0-p5.sound.js-custom-build
Open

feat: added the logic for generating reference docs from local custom build of p5.sound.js#1223
kunstewi wants to merge 2 commits intoprocessing:2.0from
kunstewi:2.0-p5.sound.js-custom-build

Conversation

@kunstewi
Copy link
Contributor

@kunstewi kunstewi commented Mar 9, 2026

fixes #1224

while working on p5.sound.js codebase I saw no option to test the generated docs locally from a local build of p5.sound.js although dummy console.log was present but no logic.

if (useExternalP5Sound) {
console.log('Cloning separate p5.sound repo');

the logic is present for p5.js builds, we can test local builds of p5.js.

// If we're using a custom build of p5 instead of a public release, create
// a build and copy it to the specified path
if (process.env.PUBLIC_P5_LIBRARY_PATH) {
await createP5Build('p5.js', `../../../public${ process.env.PUBLIC_P5_LIBRARY_PATH}`);
}

so i implemented the p5.sound.js local build testing the same way it's for p5.js by specifying the p5.sound.js local build path at LOCAL_P5_SOUND_PATH variable in .env file.

@ksen0 please take a look whenever you have time.

Thanks a lot for your time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

X Tutup