You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be better to remove extra deps (babel for gulpfile, gulpfile.babel.js, gulp, gulp-webserver, etc) and extra files / configuration. Currently the advantage of using this setup is because it easy to spin up after running a webpack production build, which is a key component of the demo task since the production webpack config build doesn't have a webserver configuration. It has the API routing to dev and index.html fallback (needed for SPA's).
Perhaps this just needs an if / else option in the production config?
The text was updated successfully, but these errors were encountered:
thescientist13
changed the title
use built in webpack-dev-server to be used instead of Gulp Webserver
use built in webpack-dev-server to be used instead of Gulp Webserver for demo task
Sep 21, 2016
thescientist13
changed the title
use built in webpack-dev-server to be used instead of Gulp Webserver for demo task
use built in webpack-dev-server instead of Gulp Webserver for demo task
Sep 30, 2016
It would be better to remove extra deps (babel for gulpfile, gulpfile.babel.js, gulp, gulp-webserver, etc) and extra files / configuration. Currently the advantage of using this setup is because it easy to spin up after running a webpack production build, which is a key component of the
demo
task since the production webpack config build doesn't have a webserver configuration. It has the API routing to dev andindex.html
fallback (needed for SPA's).Perhaps this just needs an if / else option in the production config?
The text was updated successfully, but these errors were encountered: