react-proxy

Proxies React components without unmounting or losing their state

by gaearon

Star on GitHub Forknpm

JavaScript

454 stars 43 forks 13 contributorsQuiet · 5y agoSince 2015 v2.0.8

Meet the team

See all 13 on GitHub →

gaearon191 contributions

akorchev8 contributions

Restuta1 contribution

BenoitZugmeyer1 contribution

colinmeinke1 contribution

technicallyfeasible1 contribution

knpwrs1 contribution

nhunzaker1 contribution

Languages

View on GitHub →

JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

1 of 6 standards met

Community profile →

✓README○License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 9 in progress · Last activity 5y ago

See all on GitHub →

Missing LICENSE file in the repo of ver 1.1.8OpenIssue

Currently I'm using react-proxy version 1.1.8, but can't find a LICENSE file in the repo of ver 1.1.8. Could you add the LICENSE file in the repo of ver 1.1.8? Thanks in advance.

itsuki-murata · 1y ago

Es2015 tests setupOpenPR

wkwiatek · 3y ago

Does not work with React 16.3 forwardRefOpenIssue

Please excuse a somewhat vague report as I’m just investigating a rather involved build system. Our codebase has (a) a custom component base class, which is generally discouraged; and (b) HOCs that use the new functionality. This lead to a very strange breakage when I tried to migrate some components that currently use our internal to instead extend (or ) directly: our React Native app crashed in react-proxy’s update() function with the error . It appears that when extending the React classes, the component ends up being not a class, but instead an object with the shape (per Chrome debugger) It’s not clear to me why this does not happen with our custom base class: I suppose treats it differently, being a full-blown ES6 class as opposed to what React provides. It’s also not clear to me exactly where I should be filing this bug: , , , …? Any thoughts welcomed.

haggholm · 7y ago

Recent fixes

View closed PRs →

Failing tests for auto-binded class methods defined via arrow functions.MergedPR

I scetched some tests that follow pattern that I use to define auto-binded method in ES6 classes. I tried to highlight the problem I have encountered using previous version of React Hot Loader. The tests could be wrong, I just wanted to add some illustration to my feature request. It would be awesome if the new version of Hot Reloader could handle this case.

nikolaymatrosov · 4y ago

point length property of instance methods to length of actual method implementationMergedPR

should fix https://github.com/gaearon/react-hot-loader/issues/329 in react-hot-loader@next @gaearon can you take a look?

nfcampos · 6y ago

Structured data for AI agents

Repository: gaearon/react-proxy. Description: Proxies React components without unmounting or losing their state Stars: 454, Forks: 43. Primary language: JavaScript. Languages: JavaScript (100%). Latest release: v2.0.8 (10y ago). Open PRs: 9, open issues: 16. Last activity: 5y ago. Community health: 28%. Top contributors: gaearon, akorchev, Restuta, BenoitZugmeyer, colinmeinke, technicallyfeasible, knpwrs, nhunzaker, wkwiatek, Yomguithereal and others.