|Number of watchers on Github||8264|
|Number of open issues||16|
|Average time to close an issue||4 days|
|Average time to merge a PR||1 day|
|Open pull requests||24+|
|Closed pull requests||44+|
|Last commit||over 1 year ago|
|Repo Created||over 3 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||coryhouse|
|Do you use react-slingshot? Leave a review!|
|View open issues (16)|
|View react-slingshot activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
A comprehensive starter kit for rapid application development using React.
npm startto start development in your default browser.
npm run buildto do all this:
git clone https://github.com/coryhouse/react-slingshot.git.
npm run setup
npm start -sThis will run the automated build process, start up a webserver, and open the application in your default browser. When doing development with this kit, this command will continue watching all your files. Every time you hit save the code is rebuilt, linting runs, and tests run automatically. Note: The -s flag is optional. It enables silent mode which suppresses unnecessary messages during the build.
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
npm install- If you forget to do this, you'll see this:
babel-node: command not found.
brew install watchmanif you are having the following error after an initial
npm start -s: ```sh 2017-09-05 00:44 node68587 FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22) 2017-09-05 00:44 node68587 FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22) events.js:160 throw er; // Unhandled 'error' event ^
Error: Error watching file for changes: EMFILE at exports._errnoException (util.js:1022:11) at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)
npm run analyze-bundle- Thanks @nickytonline
Thanks so much to the many contributors that made 6.0 possible!
Another major release with tons of tweaks and improvements! Thanks to everyone for contributing!
npm run test:cover. Open detailed coverage in browser via
npm run open:cover.
Merged pull requests: