You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
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 inscripts/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 mainp5.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 thescripts/parsers/in
folder after it's done? (Possiblyscripts/parsers/out
too?)Steps to reproduce
npm run build:reference
npm run dev
Would you like to work on the issue?
Someone else can take this on if desired!
The text was updated successfully, but these errors were encountered: