leecade / leecade/fe

An in-range update of react-hot-loader is breaking the build 🚨

Open
#93 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
15
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Version 3.0.0 of react-hot-loader was just published.

Branch Build failing 🚨
Dependency react-hot-loader
Current Version 3.0.0-beta.7
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

react-hot-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • ci/circleci Your tests failed on CircleCI Details

Release Notes v3.0.0
  • Add React 16 support (#629, #658)
  • Remove RedBox as default error catcher (#494)
Commits

The new version differs by 86 commits.

  • 5973747 Merge pull request #658 from gaearon/react-16
  • 80136ac v3.0.0
  • 7a968b6 refactor: revert HotContainer for now
  • 6d0346f feat: expose AppContainer with warning
  • 7d0e0da docs: remove coverage badge
  • 429cc4a docs: improve README
  • 3338ce2 feat: React 16 compatibility
  • 47ccb0a Merge pull request #655 from theKashey/master
  • b964851 document HOC Troubleshooting
  • 00404dd docs: keep AppContainer in doc
  • 60503a7 Merge pull request #639 from gaearon/hot-container
  • 7d1d294 Rename AppContainer into HotContainer
  • 2679e73 Merge pull request #494 from gaearon/no-redbox
  • 31fba04 Remove RedBox as default error catcher
  • ac52cd9 Merge pull request #608 from theKashey/master

There are 86 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Greenkeeper branch and the linked CircleCI and AppVeyor build results to reproduce the failure after react-hot-loader 3.0.0. Trace the failing project integration and determine the compatibility change needed; done means the dependency update no longer breaks the build and both listed CI checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
build-system, ci-cd, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.