Separated build-webpack from build-assets for being able to run fast css rebuilds
What does this MR do?
Running build-assets takes forever. Rebuilding webpack shouldn't be done every minute or so when editing CSS files, so I separated the yarn part into a separate file called build-webpack.
How confident are you it won't break things if deployed?
It's for the dev environment. Haven't tested, but all seems logical and don't expect a problem.
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s))