The io.js codebase has been rebranded as "Node.js", so moving forward everyone should install the latest version of Node. The name "io.js" is no longer.
nvm is way better than homebrew for managing node installations:
- can install multiple versions
- can choose which version of node to install
- easy to clean up under ~/.nvm
- there are still some rough edges with /usr/local on El Cap -- nvm avoids those altogether
Clarify that io.js is the modern version of Node and explain a little more about how to get set up with nvm, and that it lets you switch between multiple io.js/node versions.
This is in preparation for open sourcing React Native for Android.
Also add hyphens to URLs for consistency. This can break people's
browser bookmarks but it's better to be consistent and we can
redirect to docs: https://github.com/facebook/react-native/issues/2137
Test plan: Ran the website locally using `cd website; npm start`
and checked all pages render correctly.
http://i.imgur.com/RrPNgRr.png
Will update "Getting Started", "Tutorial", "Debugging" and
"Testing" separately.
It's pretty straightforward -- io.js is available through Homebrew so all you run is `brew install iojs` and then you can still run `node` from the command line. Also mentioned nvm since it's really good for switching between Node/io.js versions.
It doesn’t seem like a good practice to tell people to create their custom
ReactComponent directory inside of the Pods/ directory. The Pods/ directory
should be limited to CocoaPods installed content, and it’s not even
accepted across the board to [check this stuff into git][1]
Therefore, let’s tune the EmbeddableApp tutorial to instruct users to
create a ReactComponent directory at the root of their project. From there,
we’ll start the development server packager to source that directory as
a JS files root. This change also improves starting this packager server,
proxying the command through npm.
[1]: 5883804e6c/Objective-C.gitignore (L20-L26)
