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.
This PR is aimed to implement react RFC reactjs/rfcs#74
As long as there is no activity on the original RFC, and there is no way to introduce that comparison to the already published version I am going to....
Use webpack loader to inject necessary changes into the React-Dom
🙌 🙌 🙌 🙌 🙌 🙌
And it's actually working, letting us support any React Feature from the past or the future.
React.lazy
(build-in)It would
import
lazy automaticaly, providing auto-reloading of the changed chunks.React.memo
(requires patch) Now it could deep-force-update even memo-ed components, working with fiber directly. (landing additional prop on memoizedProps to bypass shallow equal)
React.forwardRef
(requires patch) Now it could update components, working with fiber directly
Hooks
(requires patch) Could work with hooks with
pureSFC
enabled, orignoreSFC
activated