processing / processing/p5.js-website
Vite is trying to compile the scripts/parsers/in contents
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 96
- Forks
- 322
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 8
Description
Most appropriate sections of the p5.js website?
Other (specify if possible)
What is your operating system?
Windows
Web browser and version
N/A
Actual Behavior
When running npm run dev, sometimes we run into Vite errors because it's trying to compile the js code in scripts/parsers/in and you get an error message from the internals of p5.sound. @lukeplowden and I have also found that the time from starting the dev server to being able to load the site is noticeably faster (at least on windows) after deleting the contents of that folder.
Expected Behavior
The scripts/parsers/in folder is mostly just used to produce the reference material. So far, we keep it around based on the assumption that cloning and setting up the main p5.js would be slower if we didn't, but we don't update the website reference all that often (just when a new version is released) compared to how often we make other changes to the site. So maybe it would be best if the reference parser script clears out the scripts/parsers/in folder after it's done? (Possibly scripts/parsers/out too?)
Steps to reproduce
- Build the reference from
npm run build:reference - Launch the dev server with
npm run dev
Would you like to work on the issue?
Someone else can take this on if desired!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running npm run build:reference and npm run dev, then inspect how scripts/parsers/in and possibly scripts/parsers/out are handled by the reference build and Vite. Confirm that the reference workflow no longer causes Vite to compile unnecessary parser contents and that both commands complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vite
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100