Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use built in webpack-dev-server instead of Gulp Webserver for demo task #9

Closed
thescientist13 opened this issue Sep 6, 2016 · 1 comment · Fixed by #64
Closed

use built in webpack-dev-server instead of Gulp Webserver for demo task #9

thescientist13 opened this issue Sep 6, 2016 · 1 comment · Fixed by #64

Comments

@thescientist13
Copy link
Member

thescientist13 commented Sep 6, 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 and index.html fallback (needed for SPA's).

Perhaps this just needs an if / else option in the production config?

@thescientist13 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 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
@thescientist13
Copy link
Member Author

can just use http-server with a proxy option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

1 participant