fix: use "api.isRecorded" instead of "module.hot.data" #1569
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We should not use
module.hot.data
, which is highly unreliable. Plugins like lazy-compile-webpack-plugin use a dummy loader to prevent webpack from building async modules, the module will be compiled and hot-update on demand. In such a case, themodule.hot.data
is truthy but the record does not exist, which will cause a running error inapi.reload
. I thinkapi.isRecorded
is more reliable and reasonable.