Signed-off-by: Julius Härtl <jus@bitgrid.net>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>

Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>

This avoids issues when multiple entrypoints try to asynchronously load chunks on the same page

Signed-off-by: Julius Härtl <jus@bitgrid.net>

Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

Then we can include all server repo webpack configs in 1 go

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

* Use webpack to bundle the core systemtags so the webserver can serve
them statically
* Bundle the core scss in there as well (saves a request)

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

For #13608

Since we have webpack anyway it make sense to let webpack do the
bundling instead of ourselfs. This leads to minified code (so less
transfer). And the webserver can just handle the request.

As a bonus we get a map file so debugging is easier than with our
JSCombiner stuff.

Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>