You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of inferno-mobx.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
All modules have been renamed from .mjs to .esm.js for better Webpack 4 compatibility. #1296
fe: ( inferno/dist/inferno.dev.mjs => inferno/dist/inferno.dev.esm.js )
Safari7, IE9 and PhantomJS support has been dropped. These browsers might or might not work, they are not tested anymore.
Better typescript support
Typescript support has been improved. PR d7f0408
It resolved the following issues: #1209#1295#686
All tests are now run using inferno-compat on/off to have better compatibility with React.
You can now use npm run test:browser:debug to debug inferno tests using your favorite browser
Inferno-core
Fixes the issue where hoisted Components might unnecessarily get re-mounted
Removed side-effects from patchKeyedChildren. This fixes the issue where dom nodes become null.
Fixes bug where it was possible to patch same DOM twice by chaining setStates
Fixes IE10-IE11 exception when calling render asynchronously in strict mode (TypeError: Invalid calling object)
Inferno-compat + SSR
Fixes bug where className attribute was rendered to output html
Inferno-compat
Added simple polyfills for Event.isPropagationStopped and Event.isDefaultPrevented methods
Inferno-router
deprecated: IndexLink and IndexRoute components have been removed. Replace them with Link and Route
Inferno-mobx
Updated Inferno-mobx to support Mobx v4
Inferno-devtools
initDevTools is no longer called automatically. #1289
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Version 4.0.0 of inferno-mobx was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of inferno-mobx.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
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 🌴