-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
How to - Develop #26
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
Comments
TL;DR of contents: The The watch mode, as the name suggest, watches your filesystem for changes in the files that webpack cares about in its bundle. If a file is changed, webpack automatically rebuilds the bundle and sends it to the client via the dev server. Should we also touch on HMR in this section possibly? |
I ended up stubbing how to develop? kind of article at my Antwar based prototype. It would cover I actually have a related chapter here. If we can keep the site pages simple and link to external resources at the end, that would get us pretty far I think. |
Yeah that sounds very reasonable |
Including the documentation about the API of webpack-dev-server would be better. |
I'm helping maintaining WDS, and looking through the issues, these occur the most:
I'll try to write some documentation soon (1-2 weeks) on this part. |
@SpaceK33z There's a separate issue related to Docker (#44). I expect similar articles for the rest (proxying, Vagrant) would work too. Small, focused "how tos" would be great. |
So in #78 I've written some documentation on how to use it with Vagrant. I noticed that the current documentation of WDS is not yet ported. Is this something I could work on? If yes, where would this documentation live? Maybe in |
Yeah, that would be great. The suggested articles would work well. |
I'm currently working on this, if anybody wants to help, please discuss first to prevent duplicate work. |
Add content for "how to develop" Closes webpack#26.
update title
Stub.
Feel free to comment here if you have ideas on what this guide should cover. Link to potential resources too.
The text was updated successfully, but these errors were encountered: