-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Builds should clean the build
directory before each npm run build
task
#700
Comments
I'll add this removal as a plugin to the webpack's config since it's the safest way, because we know exactly the output directory and this is the last step of building the editor. |
Hmm. But assuming, that nobody will call the |
I would use webpack plugin to do this and leave |
And like you said, it'll give a developer some insights, that this part is needed for some reason. |
The problem here is not critical. Nothing bad will happen if some old language files will be kept. So it's not a problem if people would forget about this somehow. The second point is that only the Installing a separate webpack plugin to solve accountability of another piece of code is not a good solution. It reminds me grunt times when everything was maintained in a configuration meaning that configuration was crucial to do things right. And configuration is already hard to maintain. Every change like the one proposed in ckeditor/ckeditor5-build-balloon#5 needs to be then copied to every place where we document our plugin's usage. And everyone who already had it configured would need to know that something has changed. |
I have to agree with you. I'll try to do it nicely on the |
Fix: Added language directory cleaning before each webpack build. Closes ckeditor/ckeditor5#700.
For now, running
npm run build
inside one of out three builds just adds webpack output files to thebuild
directory. After merging the #624, it became dangerous, because loading old translation files with the new editor will blow up the UI labels.The text was updated successfully, but these errors were encountered: