In the Moving to React blog post, it notes the following about the future of React in Atom:
“The new editor is faster in a number of ways, but we still have work to do before we’re totally satisfied with performance. The improved structure of the code will put us in a good position to apply more optimizations going forward. We also plan on switching Atom’s workspace and pane system to React, which will eliminate our dependency on jQuery in core and allow packages to implement their views as React components. However, packages will never be required to use React. We’ll support SpacePen for backward compatibility with existing views, and we’ll be exploring some ideas for making Atom more view-framework-agnostic for packages.”
I am trying to use React in Atom right now. It’s a little gross because there’s a mix of React and SpacePen that I modeled after
react-editor-view.coffee. The bigger issue is that I cannot use React’s event handling. I discovered that the
react-atom-fork has the following description:
"description": "Minimal, Atom-specific fork of React. Allows us to opt out of selection restoration and event dispatch.",
Presumably this is why using
onKeyDown in React fails with the following mysterious error:
Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.
"repository" in the
package.json is listed as the original Facebook repository rather than a public GitHub repo where we can see how the fork has evolved. This also makes it difficult to produce a “non-minified dev environment” so I can figure out where my error is coming from.
Could you please provide some insight as to where things are going with respect to React? Is the fork a temporary measure? Can we ultimately expect to be able to use all of its API?