Move merged-share-backend to webpack
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>
Showing
- core/js/dist/share_backend.js 0 additions, 0 deletionscore/js/dist/share_backend.js
- core/js/dist/share_backend.js.map 0 additions, 0 deletionscore/js/dist/share_backend.js.map
- core/js/merged-share-backend.js 9 additions, 0 deletionscore/js/merged-share-backend.js
- core/js/merged-share-backend.json 0 additions, 11 deletionscore/js/merged-share-backend.json
- core/webpack.common.js 64 additions, 44 deletionscore/webpack.common.js
- core/webpack.dev.js 6 additions, 4 deletionscore/webpack.dev.js
- core/webpack.prod.js 6 additions, 4 deletionscore/webpack.prod.js
- lib/private/Share/Share.php 1 addition, 1 deletionlib/private/Share/Share.php
core/js/dist/share_backend.js
0 → 100644
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
core/js/dist/share_backend.js.map
0 → 100644
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
core/js/merged-share-backend.js
0 → 100644
core/js/merged-share-backend.json
deleted
100644 → 0
Please register or sign in to comment