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
In order to do a number of things, we need to be able to access modules we currently consider internal. The main need for this comes from components or other "plugins" that need to do more than usual. For example, ReactTransitionGroup accesses ReactChildren.
We don't currently want to package ReactTransitionGroup in React itself so the only option is to build it as a standlone package. We can do that but without some substantial changes (or some hacks that probably won't work everywhere), we can't do it without also packaging up React. So we need a public API where we can make this work less awkwardly.
More soon, just wanted to make sure we had this filed.
The text was updated successfully, but these errors were encountered:
In order to do a number of things, we need to be able to access modules we currently consider internal. The main need for this comes from components or other "plugins" that need to do more than usual. For example,
ReactTransitionGroup
accessesReactChildren
.We don't currently want to package
ReactTransitionGroup
inReact
itself so the only option is to build it as a standlone package. We can do that but without some substantial changes (or some hacks that probably won't work everywhere), we can't do it without also packaging upReact
. So we need a public API where we can make this work less awkwardly.More soon, just wanted to make sure we had this filed.
The text was updated successfully, but these errors were encountered: