-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Build directory not cleared before build "all" targets #5588
Comments
The |
keen to do all this @epreston ? I'd love to have this. |
On the way. |
Ready for review. A little re-org for clarity and the normal clean-up logic on "build all". |
Fully agree, but we still lack |
Yes, I got hit by this yesterday and it took me a while to figure out what is missing. It'd be great to add. |
On the way. |
@willeastcott , @mvaligursky , @kungfooman A command already exists to build types after the library is built.
It is defined as:
You can be confident that it is clean because the first command purges the directory. Correction: it does not purge the types directory. There's a misconfiguration / expectation that needs discussion. |
Hi interesting .. personally I'd remove the publish target and make the build do this. |
Can I speed up the build 10x first by swapping a few rollup plugins ? Then we add to it ? The best in class plugin for this at the moment does both at the same time. Worth taking a look at. |
Sure, create a separate issue / pr and go for it, keen to see what it is. |
Build directory is not cleared before rebuilding all targets.
Normally, the expectation is that:
Options:
Example for rollup.config.mjs in the default export
I ran into an issue that confused me when I thought some files were not being built. They are no longer part of the build but were left there from 3 weeks ago. Clearing the directory on full builds will ensure this does not happen again.
It will also ensure extra files are not published to npm bloating the bundle size. For example "common.js" in the shaders directory, removed in a commit a few weeks ago, in a recent publish.
The text was updated successfully, but these errors were encountered: