akxcv/vuera

ReactDOM.createPortal instead of ReactDOM.render

Open

#17 opened on Oct 16, 2017

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (4,260 stars) (264 forks)batch import
enhancementgood first issuehacktoberfesthelp wanted

Description

Did you already try the new ReactDOM.createPortal as replacement for ReactDOM.render?

The benefits would be to have only 1 react app for all ReactInVue components (instead of N reacts apps, one for each ReactInVue component). Also one would be able to define a single react context to be used by all ReactInVue components. Maybe this will have some (positive) impact on your planned Benchmark #16?

Contributor guide

Tech stack
javascriptreactvue
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React fundamentalsVue basicsReact Portalsvuera architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current implementation of rendering React components inside Vue, likely in files like `src/ReactInVue.js`. Explore how ReactDOM.createPortal works and whether it can replace the current ReactDOM.render calls. Check comments on this issue for additional context, and verify React >=16 compatibility. Consider the implications for React context propagation.