Ensure atom-react-preview behaves well with create-react-app boilerplates

[dhartford]

Hi Team, Although I usually don't want to push one project's behavior on another project, in the case of Facebook's own 'create-react-app' I would like to evaluate how to get atom-react-preview to work by-default without needing changes.

As of July 2017: atom 1.1.8 atom-react-preview 2.0.0 create-react-app 1.3.3

For example, atom-react-preview 2.0.0 doesn't play well with the App.js created from running create-react-app until you change the filename extension so it becomes App.jsx

There seems to be a couple other nuances to evaluate, so placeholder ticket.

---

how to recreate: #install create-react-app globally npm install -g create-react-app #go to per-project folder to initialize the boilerplate/scripts create-react-app hello-world #to find the version of create-react-app in use, eample version 1.3.3, manually review tree npm list -g #alternatively, if on a linux-based system: npm list -g | grep create-react-app #use atom.io with atom-react-preview component to ctrl-shift-m on the default src/App.js