-
Notifications
You must be signed in to change notification settings - Fork 213
Update dependency react-hot-loader to v4 #767
Conversation
As mentioned in the original PR #724 (that was mistakenly autoclosed by Renovate)... The way to integrate react-hot-loader has changed significantly with v4: On the plus side the entrypoint patch file no longer needs to be added, which will simplify the Neutrino configuration at least :-) |
Yep! I also want to make this a little more dynamic by pulling in the version that the user installs, rather than the one we install, like a peerDependency, if it exists in the user's package.json. |
0647a0d
to
b3a8f99
Compare
139601e
to
630f642
Compare
630f642
to
56c1739
Compare
acd271d
to
9b6e4a6
Compare
3e7507c
to
ea524cf
Compare
ea524cf
to
18d6d60
Compare
Closing as I am going to take care of this in a more comprehensive PR. |
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 4.x releases. However, if you upgrade to 4.x manually then Renovate will then reenable updates for minor and patch updates automatically. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
) See: https://github.com/gaearon/react-hot-loader#migrating-from-v3 Also removes the `hotEntries` option. Closes #767.
This Pull Request updates dependency react-hot-loader from
^3.1.3
to^4.0.0
Release Notes
v4.2.0
Compare Source
v4.1.3
Compare Source
v4.1.2
Compare Source
Bug Fixes
v4.1.1
Compare Source
Bug Fixes
v4.1.0
Compare Source
Bug Fixes
v4.0.1
Compare Source
Features
Bug Fixes
_this3
(#928)v4.0.0
Compare Source
Bug Fixes
This PR has been generated by Renovate Bot.