mastofe

commit: 3d4e21f1ecd001d82e8363eb7d4086c7fc6064ba
parent: 68dca26a5d36eacb7d7e691635a14b6562ba7cf1
Author: unarist <m.unarist@gmail.com>
Date:   Sun, 25 Jun 2017 19:52:42 +0900

Don't set ASSET_HOST on build:development (#3936)

Setting ASSET_HOST to `http://0.0.0.0:8080` makes urls in manifest.json to
be invalid, e.g. `http://0.0.0.0:8080/packs/application.js`.

Anyway, we don't need set this on build:development because assets would
be delivered from same origin in development (and w/o dev-server).
Diffstat:
M
package.json
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package.json b/package.json
@@ -3,7 +3,7 @@
   "license": "AGPL-3.0",
   "scripts": {
     "postversion": "git push --tags",
-    "build:development": "cross-env RAILS_ENV=development ASSET_HOST=http://0.0.0.0:8080 ./bin/webpack",
+    "build:development": "cross-env RAILS_ENV=development ./bin/webpack",
     "build:production": "cross-env RAILS_ENV=production ./bin/webpack",
     "manage:translations": "node ./config/webpack/translationRunner.js",
     "start": "rimraf ./tmp/streaming && babel ./streaming/index.js --out-dir ./tmp && node ./tmp/streaming/index.js",