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

Add webpack-dev-server support #8

Open
mlegenhausen opened this issue Dec 11, 2015 · 3 comments
Open

Add webpack-dev-server support #8

mlegenhausen opened this issue Dec 11, 2015 · 3 comments

Comments

@mlegenhausen
Copy link
Contributor

Current the generated files are not available when using the webpack-dev-server. Is there a way to make the generated files available in the in-memory representation of the dev-server?

@nickjj
Copy link
Owner

nickjj commented Dec 11, 2015

Hi, making it available to the dev server is possible but I think doing so is out of scope for the plugin.

For example, this is a working Python/Flask example that uses webpack along with this plugin to serve md5'd assets with the dev server:

https://github.com/nickjj/demo-for-chattanooga-python-user-group

The python code that introduces the template tags can be found here:

https://github.com/nickjj/flask-webpack

If you have a better idea on how to pull this off, I'm certainly open to suggestions.

@mlegenhausen
Copy link
Contributor Author

I am using it for creating the Web App Manifest, cause of changing assets paths after webpack processing. Or do you know another approach how to manage such path containing files with webpack?

@nickjj
Copy link
Owner

nickjj commented Dec 11, 2015

Oh, so the main concern you have is you need to restart the dev server if you add/remove assets? I do agree having to do this is annoying. It will pickup edits of existing files, but not new ones.

Haven't figured out how to do this yet.

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

No branches or pull requests

2 participants