Comments (9)
https://github.com/webpack/enhanced-require/wiki/HCR-Spec
from webpack.
Interesting. I am using the LiveReload app, which does full page refresh operations a lot, but that doesn't bother me.
I am also using yeoman
and angular.js
, which can LiveReload my client, but I haven't patched-in my custom Express server yet. I also haven't experimented with your grunt task to automate my webpack
step, yet.
Problems:
-
When to check?
Most other livereload-like frameworks & tools bundle a websocket server, just to emit events when source changes. That seems like a pretty big dependency to add to Webpack, but polling for changes seems like an outdated solution. What do you think? You said you have a prototype version, how did you implement it there?
from webpack.
The "prototype" is [email protected]
and only work on node.js, where I offer FileWatchers (watch: true
) or manual checking (.check(cb)
).
For webpack I plan to offer polling (every 10 minutes in production should be not problem, an update is not so important) and manual checking (so you could send a event if you have already some kind of bidirectional connection).
The grunt task does nothing special. It just runs webpack. (grunt's watch task is worse than webpack's)
Full page refreshing is already availible through the webpack-dev-server
.
The impl plan is to emit special update files to the output directory, which contain all info regarding the update. There will be one main update file <old-hash>.update.js
and updates for the chunks <x>.<old-hash>.update.js
. Only modules that were updated are contained in these packages and the main file contains info about the new hash and existing update chunks.
The client can check existance of the main update file and download it. Than it can download the needed update chunks. When this is finished an update is availible and can be applied. If it can't be applied the app may display some info to do a whole page refresh.
To create these update files webpack need to know old module ids, old content hashes and the old bundle hash. So we need to use a hot reploading file which stores the info (--hot <file>
, { hot: <file> }
).
from webpack.
This feature is really crazy ^^
from webpack.
Yes it's crazy...
Here is more explanation:
All goals above have been reached.
Only modules (or module chains) which have opt-it (using the module API) can be replaced. An update will abort if any updated module havn't opt-in.
One can use the management API to start an update: module.hot.check(function(err, renewedModules) { /* ... */ });
If no update found renewedModules === null
.
Elsewise it will download hot update chunks for each loaded chunk. After the update have been downloaded, the hot replacement code will determine modules that will be renewed. Then:
- the old modules are disposed,
- the new code is installed,
- the accept handlers are called, and
- the self accepted modules are required.
API: https://github.com/webpack/docs/wiki/hot-code-replacement
It must be globally enabled with --hot
/ options.hot = true
.
If one don't write own management api code, one can use prepared code in the webpack/hot folder:
webpack/hot/dev-server
for the webpack-dev-server.
webpack/hot/poll
uses polling to find a update. (poll?10000
to specify a interval in ms)
Simple add it as entry:
module.exports = {
entry: ["webpack/hot/poll?600000", "./entry.js"]
// ...
};
webpack "webpack/hot/poll?600000" ./entry.js bundle.js --hot --records-path records.json
The style-loader
and mocha-loader
automatically generate hot-replaceable code.
So a stylesheet can be changed without a full page refresh and tests with changed dependencies rerun.
TODOs:
- do not download empty update chunks
from webpack.
so integrated in my app at the page router with 10 LOC... App can update itself without full page refresh...
Thanks to @Phoscur for proposing the best feature ever! 😄
from webpack.
added a demo to http://webpack.github.io/example-app/
there are 2 updates.... you can apply them with the two buttons on the right.
from webpack.
Here is a graphical example:
Compile time
Left: first compilation
module 4 changed: async require to module 10 removed
module 9 changed: normal require to module 12 added
Right: second compilation including Hot Update Chunks
Runtime
Assuming module 4 accepts itself and module 2 accepts module 3.
- Disposing modules: 3, 4, 5, 6, 8, 9, 10, 11
- Calling accept handler in module 2 (accepting module 3)
- Require self-accepted module 4
from webpack.
Thank you for doing this.
from webpack.
Related Issues (20)
- Too many logs by DefinePlugin HOT 2
- ERROR in Can't find self.__WB_MANIFEST in your SW source.
- [ProvidePlugin] force load modules whether use it or not HOT 1
- Problem with namespace import + default object destructuring getting mangled in export but not resolved in destructuring HOT 3
- Webpack not removing unused side-effect-free library from build HOT 1
- When can a patch release be published for the default mangle bug fixed last week in master? 5.92.0 and latest 5.92.1 are still broken HOT 2
- webpack5 devtools hidden-source-map does not generate sourcemap HOT 1
- hmr might fail if there are new initial chunks HOT 1
- Modules builded by Webpack dont work with SSH HOT 2
- angular 18: registerQuery in layout.mjs crashes in Production bundles. HOT 1
- Module federation prevents to use expose-shared modules as singletons HOT 3
- Improve access to resolver data in `module.rules` and `rule.use` HOT 1
- DefinePlugin breaks references to imports HOT 1
- Live reload of index.html not working after subsequent edits HOT 2
- Require is not defined in ES module scope, you can use import instead HOT 3
- PnP API is not discovered when compiling file from different directory, leading to Module not found error HOT 2
- Issue while bundling library type "module" in entries HOT 1
- Allow instantiation of WebAssembly module with `SharedArrayBuffer` memory HOT 3
- Webpack v5 keeps on compiling
- Give error as hexoid is not a function HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webpack.