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.

Sign up for GitHub

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

Jump to bottom

Investigate live reloading / hot module replacement / webpack-dev-server #864

Closed
jonathanolson opened this issue Feb 6, 2020 · 2 comments
Closed

Investigate live reloading / hot module replacement / webpack-dev-server #864

jonathanolson opened this issue Feb 6, 2020 · 2 comments
Assignees
@jonathanolson @samreid
Labels
chipper:es6-modules

Comments

@jonathanolson
Copy link
Contributor

For es6 modules, it would be good to see if webpack-dev-server can create faster iteration times.

(SR, JO, ??, low overhead during sim dev, 2 hours?) [Sprintable, post-publication. But good to do early on while concrete is wet.] Experiment with live reloading and hot module replacement. To optimize iteration time. See #845
JO: Unclear whether single entry point vs multiple vs all (sims) would be best
chrisklus added a commit that referenced this issue Feb 26, 2020
@chrisklus
Delete webpack.config.js, see #864
1d3ab17
@chrisklus
Copy link
Contributor

chrisklus commented Feb 26, 2020 •
edited
Loading

start off by looking at webpack.config.js (deleted above)

@chrisklus chrisklus mentioned this issue Feb 26, 2020
Closed
@chrisklus
Copy link
Contributor

Duplicate of #845, migrating content and closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonathanolson jonathanolson

@samreid samreid

Labels
chipper:es6-modules
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jonathanolson @samreid @chrisklus