-
Notifications
You must be signed in to change notification settings - Fork 14
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
Generating API files causes unexpected babel work in unrelated repos #1439
Comments
It is curious why we have any babel code running. I'll take a look. |
Maybe |
That's what it is! Good find. Anything else for this issue? Line 616 in b9b8d46
|
That seems good. I think we were surprised that it needed to re-transpile things at an unexpected time. If it keeps happening we can investigate. Closing. |
Something is wrong with this process, because my transpiler watch process is up to date, yet the transpileAll in the generate API is taking 50+ seconds:
|
Something appears to be interfering with the caching mechanism. It thinks it needs to re-transpile things that it shouldn't. I'm going to add a Band-Aid, a flag to that tells grunt generate-phet-io-api that it can skip transpiling. |
Hasn't happened for a while. Unassigning and hoping to remember this issue next time it's in a buggy state. |
While regenerating the API for Projectile Data Lab, @samreid and I encountered the following console errors in WebStorm:
We aren't sure why running grunt generate-phet-io-api from the projectile-data-lab repo would trigger this Babel work, and would like to investigate further.
The text was updated successfully, but these errors were encountered: