Singleton lazy loading wrapper around facebook/react.
constcreateFragmentCSSTransitionGroupLinkedStateMixinPerfPureRenderMixinReactReactDOMReactDOMServershallowCompareTestUtilsTransitionGroupupdate= ;// optionalconst PropTypes = React;
// React is the default export;// Or, it's also available as a named export;
We plan to closely track the React release cycle in order to be able to use the latest features as well as provide access to React API warnings (in
atom --dev mode).
Only when a property is looked up on the
react-for-atom export is that module actually
const ReactForAtom = ;// `react` is actually required hereconst React = ReactForAtom;// `TestUtils` is actually required hereconst TestUtils = ReactForAtom;
react-for-atom version numbers were loosely related to the React version in
dependencies. From that version onward, the version of
react-for-atom matches the React version.
react-for-atom are reflected in pre-release versions (e.g.
0.14.6-1). From a semver perspective, this doesn't make sense. However, because you should pin the version of
react-for-atom anyway, this is a clear workaround for conveying React versioning info.