Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Update dependency react-hot-loader to v4 #767

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 27, 2018

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
  • always update bound functions. #​949 (7819c71)
  • Fragment with a single element. fixes #​956 (7e80881)
  • props merge order. #​967 (#​968) (1f8adb9)

v4.1.1

Compare Source

Bug Fixes
  • Proxy should keep methods own props. #​918 (a84dcd0)

v4.1.0

Compare Source

Bug Fixes
  • condition render in Fragments #​942 (#​943) (2549a18)

v4.0.1

Compare Source

Features
  • 🚀 React 16.3 support (#​918)
  • 🧙🏻‍♂️ StatelessFunctionComponents are not wrapped by Stateful components anymore (#​873)
  • 🧠Improved TypeScript support (no more than documentation) (#​884)
Bug Fixes
  • support babel temporal _this3 (#​928)

v4.0.0

Compare Source

Bug Fixes
  • proper children reconcile for nested tags, fixes #​869 (#​871) (2de4e58)


This PR has been generated by Renovate Bot.

@edmorley
Copy link
Member

edmorley commented Apr 4, 2018

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:
https://github.com/gaearon/react-hot-loader#migrating-from-v3

On the plus side the entrypoint patch file no longer needs to be added, which will simplify the Neutrino configuration at least :-)

@eliperelman
Copy link
Member

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.

@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch from 0647a0d to b3a8f99 Compare April 15, 2018 22:05
@renovate renovate bot changed the title Update dependency react-hot-loader to ^4.0.0 Update dependency react-hot-loader to v4 Apr 17, 2018
@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch 2 times, most recently from 139601e to 630f642 Compare April 27, 2018 20:41
@renovate renovate bot changed the title Update dependency react-hot-loader to v4 fix(deps): update dependency react-hot-loader to v4 Apr 27, 2018
@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch from 630f642 to 56c1739 Compare April 28, 2018 00:06
@renovate renovate bot changed the title fix(deps): update dependency react-hot-loader to v4 Update dependency react-hot-loader to v4 Apr 30, 2018
@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch 2 times, most recently from acd271d to 9b6e4a6 Compare May 5, 2018 16:05
@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch 2 times, most recently from 3e7507c to ea524cf Compare May 17, 2018 20:48
@eliperelman eliperelman self-assigned this May 19, 2018
@renovate renovate bot force-pushed the renovate/react-hot-loader-4.x branch from ea524cf to 18d6d60 Compare May 23, 2018 20:13
@eliperelman
Copy link
Member

Closing as I am going to take care of this in a more comprehensive PR.

@renovate
Copy link
Contributor Author

renovate bot commented May 23, 2018

Renovate Ignore Notification

As 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.

@renovate renovate bot deleted the renovate/react-hot-loader-4.x branch May 23, 2018 21:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

3 participants