| // Author: Artem Sapegin http://sapegin.me, 2015 | |
| (function() { | |
| var config = { | |
| paths: { | |
| lodash: '../bower_components/lodash/lodash', | |
| jquery: '../bower_components/jquery/dist/jquery', | |
| backbone: '../bower_components/backbone/backbone', | |
| react: '../bower_components/react/react', | |
| backboneLocalStorage: '../bower_components/backbone.localStorage/backbone.localStorage', |
While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.
| . | |
| ├── actions | |
| ├── stores | |
| ├── views | |
| │ ├── Anonymous | |
| │ │ ├── __tests__ | |
| │ │ ├── views | |
| │ │ │ ├── Home | |
| │ │ │ │ ├── __tests__ | |
| │ │ │ │ └── Handler.js |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
