Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vite is trying to compile the scripts/parsers/in contents #722

Open
davepagurek opened this issue Mar 12, 2025 · 1 comment
Open

Vite is trying to compile the scripts/parsers/in contents #722

davepagurek opened this issue Mar 12, 2025 · 1 comment
Labels
Bug Something isn't working

Comments

@davepagurek
Copy link
Collaborator

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

Would you like to work on the issue?

Someone else can take this on if desired!

@davepagurek davepagurek added the Bug Something isn't working label Mar 12, 2025
@kajal-jotwani
Copy link

I would like to work on this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants