React + Redux starter kit / boilerplate with Babel, hot reloading, testing, linting and a working example app built in

Overview


Build status: Linux Build status: Windows Dependency Status Coverage Status

A comprehensive starter kit for rapid application development using React.

Why Slingshot?

  1. One command to get started - Type npm start to start development in your default browser.
  2. Rapid feedback - Each time you hit save, changes hot reload and linting and automated tests run.
  3. One command line to check - All feedback is displayed on a single command line.
  4. No more JavaScript fatigue - Slingshot uses the most popular and powerful libraries for working with React.
  5. Working example app - The included example app shows how this all works together.
  6. Automated production build - Type npm run build to do all this:

React Slingshot Production Build

Get Started

  1. Initial Machine Setup

    First time running the starter kit? Then complete the Initial Machine Setup.

  2. Click "Use this template"

    Click the green "Use this template" button at the top of this page and enter a name and description for your repo.

  3. Run the setup script

    npm run setup

  4. Run the example app

    npm start -s

    This 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.

  5. Review the example app.

    This starter kit includes a working example app that calculates fuel savings. Note how all source code is placed under /src. Tests are placed alongside the file under test. The final built app is placed under /dist. These are the files you run in production.

  6. Delete the example app files.

    Once you're comfortable with how the example app works, you can delete those files and begin creating your own app.

  7. Having issues? See Having Issues?.

Initial Machine Setup

  1. Install Node 8.0.0 or greater

    Need to run multiple versions of Node? Use nvm.

  2. Install Git.

  3. Disable safe write in your editor to assure hot reloading works properly.

  4. Complete the steps below for your operating system:

    macOS

    • Install watchman via brew install watchman or fswatch via brew install fswatch to avoid this issue which occurs if your macOS has no appropriate file watching service installed.

    Linux

    • Run this to increase the limit on the number of files Linux will watch. Here's why.

      echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p.

    Windows

    • Install Python 2.7. Some node modules may rely on node-gyp, which requires Python on Windows.

    • Install C++ Compiler. Browser-sync requires a C++ compiler on Windows.

      Visual Studio Express comes bundled with a free C++ compiler.

      If you already have Visual Studio installed: Open Visual Studio and go to File -> New -> Project -> Visual C++ -> Install Visual C++ Tools for Windows Desktop. The C++ compiler is used to compile browser-sync (and perhaps other Node modules).


Having Issues? Try these things first

  1. Make sure you ran all steps in Get started including the initial machine setup.

  2. Run npm install - If you forget to do this, you'll see this: babel-node: command not found.

  3. Install the latest version of Node.

  4. Make sure files with names that begin with a dot (.editorconfig, .gitignore, .npmrc) are copied to the project directory root. This is easy to overlook if you copy this repository manually.

  5. Don't run the project from a symbolic link. It may cause issues with file watches.

  6. Delete any .eslintrc that you're storing in your user directory. Also, disable any ESLint plugin / custom rules that you've enabled within your editor. These will conflict with the ESLint rules defined in this project.

  7. Make sure you don't have NODE_ENV set to production on your machine. If you do then the development dependencies won't be installed. Here's how to check.

  8. Install watchman with brew install watchman if you are having the following error after an initial npm start -s:

    2017-09-05 00:44 node[68587] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
    2017-09-05 00:44 node[68587] (FSEvents.framework) 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)
  9. Tip: Things to check if you get an npm run lint error or build error:

    • If ESW found an error or warning in your project (e.g. console statement or a missing semi-colon), the lint thread will exit with Exit status 1. To fix:

      1. Change the npm run lint script to "esw webpack.config.* src tools; exit 0"
      2. Change the npm run lint:watch script to "esw webpack.config.* src tools --watch; exit 0"

      Note: Adding exit 0 will allow the npm scripts to ignore the status 1 and allow ESW to print all warnings and errors.

    • Ensure the eslint/esw globally installed version matches the version used in the project. This will ensure the esw keyword is resolved.

  10. Rebuild node-sass with npm rebuild node-sass if you are having and error like Node Sass does not yet support your current environment on macOS XXX after an initial npm start -s.


Technologies

Slingshot offers a rich development experience using the following technologies:

Tech Description Learn More
React Fast, composable client-side components. Pluralsight Course
Redux Enforces unidirectional data flows and immutable, hot reloadable store. Supports time-travel debugging. Lean alternative to Facebook's Flux. Getting Started with Redux, Building React Applications with Idiomatic Redux, Pluralsight Course
React Router A complete routing library for React Pluralsight Course
Babel Compiles ES6 to ES5. Enjoy the new version of JavaScript today. ES6 REPL, ES6 vs ES5, ES6 Katas, Pluralsight course
Webpack Bundles npm packages and our JS into a single file. Includes hot reloading via react-transform-hmr. Quick Webpack How-to Pluralsight Course
Browsersync Lightweight development HTTP server that supports synchronized testing and debugging on multiple devices. Intro vid
Jest Automated tests with built-in expect assertions and Enzyme for DOM testing without a browser using Node. Pluralsight Course
TrackJS JavaScript error tracking. Free trial
ESLint Lint JS. Reports syntax and style issues. Using eslint-plugin-react for additional React specific linting rules.
SASS Compiled CSS styles with variables, functions, and more. Pluralsight Course
PostCSS Transform styles with JS plugins. Used to autoprefix CSS
Editor Config Enforce consistent editor settings (spaces vs tabs, etc). IDE Plugins
npm Scripts Glues all this together in a handy automated build. Pluralsight course, Why not Gulp?

The starter kit includes a working example app that puts all of the above to use.


Questions?

Check out the FAQ

Comments
  • Implement React Router@4.0.0

    Implement React [email protected]

    Hi Cory,

    Here's your hot fresh PR. :)

    I've implemented [email protected] under branch "[email protected]/tobiahrex".

    CHANGE NOTES:

    • index.js:

      • Implemented per the docs. However I felt it cleaner to keep the Route tree out of the index.js file and in it's own component - App.js
    • App.js: Everything that was in "routes.js" is now converted (per my understanding of rrV4) and implemented here.

      • "IndexLink " is no longer an option. However "NavLink" with attr: "activeStyle" is.
      • "Switch" is for the NotFoundPage to catch anything not matched in the route tree, otherwise it's always mounted.
      • Each of the above mentioned comps are from react-router-dom since they're no longer a part of the rrV3 API.
    • configureStore.js: nothing outside of the docs except...

      • export const history = createHistory(); So the docs had the createStore() invoked in what is our "index.js" which I'm not a fan of. Since we want the same "history" instance @ both the configureStore.js & index.js to pass in as "ConnectedRouter history={history}", I thought it best to do this.
    • About, HomePage, NotFoundPage:

      • Added preceding "/" to each name.
      • Changed import source to "react-router-dom".
    • package.json:

      • npm i history --save-dev
      • npm i react-router
      • npm i react-router-redux@next --save

    Thanks for the suggestions to contribute and being open. Let me know if I can do/change anything.

    Respectfully,

    -Toby

    help wanted 
    opened by TobiahRex 55
  • error  Parsing error: The keyword 'import' is reserved

    error Parsing error: The keyword 'import' is reserved

    i cant intall this i run in my terminal 3 commands: Clone the project. git clone https://github.com/coryhouse/react-slingshot.git. Install Node packages. npm install Run the example app. npm start -s

    and terminal return this messages

    /Users/eugene/Documents/git/cit-one/webpack.config.js 4:1 error Parsing error: The keyword 'import' is reserved /Users/eugene/Documents/git/cit-one/tools/build.js 4:1 error Parsing error: The keyword 'import' is reserved /Users/eugene/Documents/git/cit-one/tools/buildHtml.js 10:1 error Parsing error: The keyword 'import' is reserved /Users/eugene/Documents/git/cit-one/tools/distServer.js 4:1 error Parsing error: The keyword 'import' is reserved /Users/eugene/Documents/git/cit-one/tools/srcServer.js 5:1 error Parsing error: The keyword 'import' is reserved ✖ 5 problems (5 errors, 0 warnings ERROR: lint:tools: None-Zero Exit(1);

    bug 
    opened by AliveDD 41
  • Start script fails after initial installation.

    Start script fails after initial installation.

    Node version: v8.1.4

    npm version: 5.0.3

    Operating system: macOS Sierra v10.12.5

    Command line used: iTerm2

    Steps to reproduce:

    • (For issue 1) 1.) npm run setup or npm install 2.) npm start -s or npm start

    • (For issue 2) After issue 1 is resolved, run npm start -s or npm start

    Issue 1: After initial installation via npm run setup or npm install, start script fails. Error output provided below.

    Error Output:

    2017-07-18 00:01 node[20270] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
    2017-07-18 00:01 node[20270] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
    events.js:182
          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:1360:11)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] test: `jest "--watch"`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] test script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_01_38_701Z-debug.log
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] test:watch: `npm run test -- --watch`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] test:watch script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_01_38_725Z-debug.log
    ERROR: "test:watch" exited with 1.
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] start script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_01_38_821Z-debug.log
    

    Issue 2: After fixing issue 1 (see above), start script fails. Error output provided below.

    Error Output:

     RUNS  src/components/FuelSavingsForm.spec.js
    [BS] Access URLs:
     -------------------------------------
           Local: http://localhost:3000
        External: http://192.168.0.22:3000
     -------------------------------------
              UI: http://localhost:3001
     UI External: http://192.168.0.22:3001
     -------------------------------------
    [BS] Serving files from: src
    [BS] Watching files...
    can't resolve reference #/definitions/basicConfig from id #
    can't resolve reference #/definitions/basicConfigOrBoolean from id #
     PASS  src/components/FuelSavingsForm.spec.jsnfigOrBoolean from id #
     PASS  src/components/FuelSavingsResults.spec.js
     PASS  src/store/store.spec.js
     PASS  src/reducers/fuelSavingsReducer.spec.js
     PASS  src/utils/fuelSavingsCalculator.spec.js
     PASS  src/actions/fuelSavingsActions.spec.js
     PASS  src/utils/mathHelper.spec.js
     PASS  src/components/AboutPage.spec.js
    
     PASS  src/components/FuelSavingsTextInput.spec.js
    
     RUNS  src/containers/FuelSavingsPage.spec.js
    /Users/branden/Documents/GitHub/react-slingshot/tools/setup/setupPrompts.js (1/0)
      ✖  6:28  Unnecessary escape character: \.  no-useless-escape
    
    ✖ 1 error (12:05:24 AM)
    
    
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] lint: `esw webpack.config.* src tools --color`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] lint script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_05_24_348Z-debug.log
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] lint:watch: `npm run lint --watch`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] lint:watch script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_05_24_377Z-debug.log
    ERROR: "lint:watch" exited with 1.
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! [email protected] start: `npm-run-all --parallel test:watch open:src lint:watch`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the [email protected] start script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /Users/branden/.npm/_logs/2017-07-18T04_05_24_482Z-debug.log
    
    opened by DaneTheory 38
  • App config

    App config

    I may be wrong but it seems react-slingshot doesn't have any sort of app config setup.

    I think it'll be nice to have something like config/environment.js where config variables for the app can be set. This way, I can easily specify different configs for multiple environments, e.g API keys, baseUrls, app feature flags, e.t.c

    Thoughts?

    opened by fayimora 36
  • Webpack 2

    Webpack 2

    OK, this is the sum total of what I did to support Webpack 2. This subsumes the PR I submitted earlier that just included the configureStore changes.

    opened by mlwigdahl 30
  • Bundle analyzer Error: listen EADDRINUSE :::8888

    Bundle analyzer Error: listen EADDRINUSE :::8888

    Node version: v6.5.0

    npm version: 3.10.3

    Operating system: macos 10.12.1

    Command line used: npm start

    Steps to reproduce:

    1, change some code under src. 2, save 3, Got the errmsg:

    webpack: bundle is now VALID.
    
    
    Unable to find bundle asset "/Users/jifeng/gitlab/cmbc/dist/bundle.js".
    Analyzer will use module sizes from stats file.
    
    events.js:160
          throw er; // Unhandled 'error' event
          ^
    
    Error: listen EADDRINUSE :::8888
        at Object.exports._errnoException (util.js:1026:11)
        at exports._exceptionWithHostPort (util.js:1049:20)
        at Server._listen2 (net.js:1253:14)
        at listen (net.js:1289:10)
        at Server.listen (net.js:1385:5)
        at EventEmitter.listen (/Users/jifeng/gitlab/cmbc/node_modules/webpack-bundle-analyzer/node_modules/express/lib/application.js:617:24)
        at Object.startServer (/Users/jifeng/gitlab/cmbc/node_modules/webpack-bundle-analyzer/lib/viewer.js:57:14)
        at BundleAnalyzerPlugin.startAnalyzerServer (/Users/jifeng/gitlab/cmbc/node_modules/webpack-bundle-analyzer/lib/BundleAnalyzerPlugin.js:78:12)
        at analyzeFn (/Users/jifeng/gitlab/cmbc/node_modules/webpack-bundle-analyzer/lib/BundleAnalyzerPlugin.js:57:24)
        at Timeout._onTimeout (/Users/jifeng/gitlab/cmbc/node_modules/webpack-bundle-analyzer/lib/BundleAnalyzerPlugin.js:69:11)
        at tryOnTimeout (timers.js:232:11)
        at Timer.listOnTimeout (timers.js:202:5)
    
    
    opened by ilife5 30
  • Deploying on Heroku

    Deploying on Heroku

    Node version: v5.0.0

    npm version: 3.3.6

    Operating system: OSX

    Command line used: Terminal

    Steps to reproduce: Clone repot. Run npm run setup. Deploy react sling-shot on Heroku. Using the four steps from the Heroku Getting Started Tutorial: https://devcenter.heroku.com/articles/getting-started-with-nodejs#deploy-the-app

    First off, thanks for the starter kit. It's been a massive help.

    I was wondering if anyone had any experience deploying react-slingshot to Heroku. I've built two apps on top of it. Both of which I found had memory leaks after running $ heroku logs --tail after trying to deploy. I wasn't sure where the memory leaks were coming from, so I started with just trying to deploy the example react-slingshot app. This also failed for what looks like a different reason.

    I'm relatively new to Heroku. If anyone who has deployed on Heroku using react-slingshot could point me in the right direction, you'd be a hero. Thanks :)

    When I log the details of launching react-slingshot, I get the following output:

    $ heroku logs --tail 2016-09-20T21:52:41.722414+00:00 heroku[api]: Enable Logplex by [email protected] 2016-09-20T21:52:41.722414+00:00 heroku[api]: Release v2 created by [email protected] 2016-09-20T21:53:21.115338+00:00 heroku[api]: Scale to web=1 by [email protected] 2016-09-20T21:53:21.116298+00:00 heroku[api]: Deploy 884be3c by [email protected] 2016-09-20T21:53:21.116404+00:00 heroku[api]: Release v3 created by [email protected] 2016-09-20T21:53:21.603620+00:00 heroku[slug-compiler]: Slug compilation started 2016-09-20T21:53:21.603625+00:00 heroku[slug-compiler]: Slug compilation finished 2016-09-20T21:53:22.582516+00:00 heroku[web.1]: Starting process with commandnpm start2016-09-20T21:53:24.423356+00:00 app[web.1]: > [email protected] prestart /app 2016-09-20T21:53:24.423342+00:00 app[web.1]: 2016-09-20T21:53:24.423357+00:00 app[web.1]: > npm-run-all --parallel start-message remove-dist 2016-09-20T21:53:24.423358+00:00 app[web.1]: 2016-09-20T21:53:24.428706+00:00 app[web.1]: sh: 1: npm-run-all: not found 2016-09-20T21:53:24.438975+00:00 app[web.1]: npm ERR! node v5.11.1 2016-09-20T21:53:24.432801+00:00 app[web.1]: 2016-09-20T21:53:24.438743+00:00 app[web.1]: npm ERR! Linux 3.13.0-95-generic 2016-09-20T21:53:24.438884+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start" 2016-09-20T21:53:24.439208+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2016-09-20T21:53:24.439045+00:00 app[web.1]: npm ERR! npm v3.10.7 2016-09-20T21:53:24.439124+00:00 app[web.1]: npm ERR! file sh 2016-09-20T21:53:24.439293+00:00 app[web.1]: npm ERR! errno ENOENT 2016-09-20T21:53:24.439364+00:00 app[web.1]: npm ERR! syscall spawn 2016-09-20T21:53:24.439433+00:00 app[web.1]: npm ERR! [email protected] prestart:npm-run-all --parallel start-message remove-dist2016-09-20T21:53:24.439699+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed. 2016-09-20T21:53:24.439494+00:00 app[web.1]: npm ERR! spawn ENOENT 2016-09-20T21:53:24.439870+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: 2016-09-20T21:53:24.439572+00:00 app[web.1]: npm ERR! 2016-09-20T21:53:24.439646+00:00 app[web.1]: npm ERR! Failed at the [email protected] prestart script 'npm-run-all --parallel start-message remove-dist'. 2016-09-20T21:53:24.439760+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the example_react_app package, 2016-09-20T21:53:24.439816+00:00 app[web.1]: npm ERR! not with npm itself. 2016-09-20T21:53:24.439922+00:00 app[web.1]: npm ERR! npm-run-all --parallel start-message remove-dist 2016-09-20T21:53:24.440030+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with: 2016-09-20T21:53:24.440082+00:00 app[web.1]: npm ERR! npm bugs example_react_app 2016-09-20T21:53:24.440132+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via: 2016-09-20T21:53:24.443565+00:00 app[web.1]: 2016-09-20T21:53:24.440182+00:00 app[web.1]: npm ERR! npm owner ls example_react_app 2016-09-20T21:53:24.440233+00:00 app[web.1]: npm ERR! There is likely additional logging output above. 2016-09-20T21:53:24.443670+00:00 app[web.1]: npm ERR! Please include the following file with any support request: 2016-09-20T21:53:24.443727+00:00 app[web.1]: npm ERR! /app/npm-debug.log 2016-09-20T21:53:24.485426+00:00 heroku[web.1]: Process exited with status 1 2016-09-20T21:53:24.499145+00:00 heroku[web.1]: State changed from starting to crashed 2016-09-20T21:53:24.500363+00:00 heroku[web.1]: State changed from crashed to starting 2016-09-20T21:53:26.160823+00:00 heroku[web.1]: Starting process with commandnpm start2016-09-20T21:53:28.528762+00:00 app[web.1]: 2016-09-20T21:53:28.528778+00:00 app[web.1]: > [email protected] prestart /app 2016-09-20T21:53:28.528779+00:00 app[web.1]: > npm-run-all --parallel start-message remove-dist 2016-09-20T21:53:28.528780+00:00 app[web.1]: 2016-09-20T21:53:28.535445+00:00 app[web.1]: sh: 1: npm-run-all: not found 2016-09-20T21:53:28.540004+00:00 app[web.1]: 2016-09-20T21:53:28.546468+00:00 app[web.1]: npm ERR! Linux 3.13.0-95-generic 2016-09-20T21:53:28.546625+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start" 2016-09-20T21:53:28.546748+00:00 app[web.1]: npm ERR! node v5.11.1 2016-09-20T21:53:28.546854+00:00 app[web.1]: npm ERR! npm v3.10.7 2016-09-20T21:53:28.546967+00:00 app[web.1]: npm ERR! file sh 2016-09-20T21:53:28.547075+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2016-09-20T21:53:28.547179+00:00 app[web.1]: npm ERR! errno ENOENT 2016-09-20T21:53:28.547283+00:00 app[web.1]: npm ERR! syscall spawn 2016-09-20T21:53:28.547372+00:00 app[web.1]: npm ERR! [email protected] prestart:npm-run-all --parallel start-message remove-dist2016-09-20T21:53:28.547536+00:00 app[web.1]: npm ERR! 2016-09-20T21:53:28.547445+00:00 app[web.1]: npm ERR! spawn ENOENT 2016-09-20T21:53:28.547626+00:00 app[web.1]: npm ERR! Failed at the [email protected] prestart script 'npm-run-all --parallel start-message remove-dist'. 2016-09-20T21:53:28.547784+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the example_react_app package, 2016-09-20T21:53:28.547859+00:00 app[web.1]: npm ERR! not with npm itself. 2016-09-20T21:53:28.547701+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed. 2016-09-20T21:53:28.547936+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: 2016-09-20T21:53:28.548008+00:00 app[web.1]: npm ERR! npm-run-all --parallel start-message remove-dist 2016-09-20T21:53:28.548082+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with: 2016-09-20T21:53:28.548155+00:00 app[web.1]: npm ERR! npm bugs example_react_app 2016-09-20T21:53:28.548227+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via: 2016-09-20T21:53:28.548300+00:00 app[web.1]: npm ERR! npm owner ls example_react_app 2016-09-20T21:53:28.548376+00:00 app[web.1]: npm ERR! There is likely additional logging output above. 2016-09-20T21:53:28.552172+00:00 app[web.1]: 2016-09-20T21:53:28.552332+00:00 app[web.1]: npm ERR! Please include the following file with any support request: 2016-09-20T21:53:28.552404+00:00 app[web.1]: npm ERR! /app/npm-debug.log 2016-09-20T21:53:28.639797+00:00 heroku[web.1]: State changed from starting to crashed 2016-09-20T21:53:28.624904+00:00 heroku[web.1]: Process exited with status 1

    opened by tvarner 28
  • Can't install dependencies using yarn

    Can't install dependencies using yarn

    Node version: 6.9.1 npm version: 3.10 yarn version: 0.22.0 Operating system: MacOs

    Command line used: yarn

    It throws the below error:

    [1/4] 🔍  Resolving packages...
    [2/4] 🚚  Fetching packages...
    warning There appears to be trouble with your network connection. Retrying...
    warning There appears to be trouble with your network connection. Retrying...
    warning There appears to be trouble with your network connection. Retrying...
    warning There appears to be trouble with your network connection. Retrying...
    warning There appears to be trouble with your network connection. Retrying...
    warning There appears to be trouble with your network connection. Retrying...
    error An unexpected error occurred: "https://artifacts.bos.rapid7.com/nexus/content/groups/npm-all/extract-text-webpack-plugin/-/extract-text-webpack-plugin-2.1.0.tgz: getaddrinfo ENOTFOUND artifacts.bos.rapid7.com artifacts.bos.rapid7.com:443".
    
    opened by haipham23 26
  • Jest Migration

    Jest Migration

    I have started a (new branch)[https://github.com/coryhouse/react-slingshot/tree/jest-migration].

    The initial move was rather painless, but here are a few steps that I would see as required before merging in this change.

    • [x] Documentation Update
      • [x] Remove unused packages
      • [x] Add jest documents and help links
    • [x] Code Coverage - [https://facebook.github.io/jest/docs/configuration.html#configuration-options-configuration]
    • [x] Add Snapshot tests (EDIT No longer stretch, this is a simple add and very nice to use. We should absolutely add at least one.)
    • [x] Address Issues with Windows build (I think this is a path issue in the script)
    • [x] Remove extra comments that were referencing chai assertions that no longer apply (I noticed reference to deep equal)
    • [ ] Create Progress Reporter (This will be addressed directly in jest, see thread on facebook/jest#2703 for more details)

    Please comment with any question or if I am missing anything that should be added to the list above.

    help wanted 
    opened by kwelch 26
  • Get error when execute

    Get error when execute "npm start" command.

    I follow the instruction and got this problem when running "npm start" command. AFAIK, root cause of this error is "npm-run-all" was not installed global. Are there anyway to run local packages from cli? I know I can manually add project's node_mobules folder to $PATH environment variable. But it isn't a best way, I have to repeat these step every project. Do you have any suggestions for me?

    
    npm ERR! Linux 4.2.6-301.fc23.x86_64
    npm ERR! argv "/usr/bin/node" "/home/nhduc/.npm-global/bin/npm" "start"
    npm ERR! node v5.10.1
    npm ERR! npm  v3.8.6
    npm ERR! file sh
    npm ERR! code ELIFECYCLE
    npm ERR! errno ENOENT
    npm ERR! syscall spawn
    npm ERR! [email protected] prestart: `npm-run-all --parallel start-message remove-dist lint:tools`
    npm ERR! spawn ENOENT
    npm ERR! 
    npm ERR! Failed at the [email protected] prestart script 'npm-run-all --parallel start-message remove-dist lint:tools'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the react-slingshot package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     npm-run-all --parallel start-message remove-dist lint:tools
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs react-slingshot
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls react-slingshot
    npm ERR! There is likely additional logging output above.
    
    npm ERR! Please include the following file with any support request:
    npm ERR!     /home/nhduc/Documents/projects/react-slingshot/npm-debug.log
    
    
    opened by nhducit 24
  • Update ESLint Config

    Update ESLint Config

    After the changes made in #405, there is a lot of eslint config now in the package.json.

    In effort to clean this up, there was a suggestion to move Slingshot to a baseline preset.

    This issue is to capture that ask and open the discussion to others about what the eslint config preset should be set to.

    Options

    • ESLint Recommended Baseline
      • Do we include other recommended baselines (ie. react, import, etc.)
    • ESList shared preset
      • Which preset?
        • AirBnB - No - too opinoinated see #35
        • CRA?
        • Standard/Standard-Semi?
    • Package Slingshot Config
      • Is the current config at a place that is right sized and can be shared as a packaged config
    help wanted Good first PR 
    opened by kwelch 23
  • Add .circleci/config.yml

    Add .circleci/config.yml

    Pull Request Template

    The code review checklist below is used for all pull requests.

    1. Review the list before submitting your pull request.
    2. Leave the list intact for the code reviewer's use.

    Checklist

    • [ ] Latest code from master has been merged into the pull request branch
    • [ ] Code is camelCased
    • [ ] No commented out code (if required, place // TODO above with explanation)
    • [ ] No linting issues
    • [ ] Automated tests exist and pass
    • [ ] Build is successful (npm run build)
    • [ ] Works in IE 11, Chrome, Firefox, and Edge

    Thanks!

    :heart:

    opened by eslamsadawi 0
  • Mybranch

    Mybranch

    Pull Request Template

    The code review checklist below is used for all pull requests.

    1. Review the list before submitting your pull request.
    2. Leave the list intact for the code reviewer's use.

    Checklist

    • [ ] Latest code from master has been merged into the pull request branch
    • [ ] Code is camelCased
    • [ ] No commented out code (if required, place // TODO above with explanation)
    • [ ] No linting issues
    • [ ] Automated tests exist and pass
    • [ ] Build is successful (npm run build)
    • [ ] Works in IE 11, Chrome, Firefox, and Edge

    Thanks!

    :heart:

    opened by HuShaker 0
  • Add .circleci/config.yml

    Add .circleci/config.yml

    Pull Request Template

    The code review checklist below is used for all pull requests.

    1. Review the list before submitting your pull request.
    2. Leave the list intact for the code reviewer's use.

    Checklist

    • [x] Latest code from master has been merged into the pull request branch
    • [x] Code is camelCased
    • [x] No commented out code (if required, place // TODO above with explanation)
    • [x] No linting issues
    • [x] Automated tests exist and pass
    • [x] Build is successful (npm run build)
    • [x] Works in IE 11, Chrome, Firefox, and Edge

    Thanks!

    :heart:

    opened by huongtinhve 2
  • Bump decode-uri-component from 0.2.0 to 0.2.2

    Bump decode-uri-component from 0.2.0 to 0.2.2

    Bumps decode-uri-component from 0.2.0 to 0.2.2.

    Release notes

    Sourced from decode-uri-component's releases.

    v0.2.2

    • Prevent overwriting previously decoded tokens 980e0bf

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

    v0.2.1

    • Switch to GitHub workflows 76abc93
    • Fix issue where decode throws - fixes #6 746ca5d
    • Update license (#1) 486d7e2
    • Tidelift tasks a650457
    • Meta tweaks 66e1c28

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump engine.io and browser-sync

    Bump engine.io and browser-sync

    Bumps engine.io to 6.2.1 and updates ancestor dependency browser-sync. These dependencies need to be updated together.

    Updates engine.io from 3.2.1 to 6.2.1

    Release notes

    Sourced from engine.io's releases.

    6.2.1

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)

    6.2.0

    Features

    • add the "maxPayload" field in the handshake details (088dcb4)

    So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSize value.

    This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), as we only add a field in the JSON-encoded handshake data:

    0{"sid":"lv_VI97HAXpY6yYWAAAC","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000,"maxPayload":1000000}
    

    Links

    6.1.3

    Bug Fixes

    • typings: allow CorsOptionsDelegate as cors options (#641) (a463d26)
    • uws: properly handle chunked content (#642) (3367440)

    ... (truncated)

    Changelog

    Sourced from engine.io's changelog.

    6.2.1 (2022-11-20)

    :warning: This release contains an important security fix :warning:

    A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

    Error: read ECONNRESET
        at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
    Emitted 'error' event on Socket instance at:
        at emitErrorNT (internal/streams/destroy.js:106:8)
        at emitErrorCloseNT (internal/streams/destroy.js:74:3)
        at processTicksAndRejections (internal/process/task_queues.js:80:21) {
      errno: -104,
      code: 'ECONNRESET',
      syscall: 'read'
    }
    

    Please upgrade as soon as possible.

    Bug Fixes

    • catch errors when destroying invalid upgrades (#658) (425e833)

    3.6.0 (2022-06-06)

    Bug Fixes

    Features

    • decrease the default value of maxHttpBufferSize (58e274c)

    This change reduces the default value from 100 mb to a more sane 1 mb.

    This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

    See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

    • increase the default value of pingTimeout (f55a79a)

    ... (truncated)

    Commits
    • 24b847b chore(release): 6.2.1
    • 425e833 fix: catch errors when destroying invalid upgrades (#658)
    • 99adb00 chore(deps): bump xmlhttprequest-ssl and engine.io-client in /examples/latenc...
    • d196f6a chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#660)
    • 7c1270f chore(deps): bump nanoid from 3.1.25 to 3.3.1 (#659)
    • 535a01d ci: add Node.js 18 in the test matrix
    • 1b71a6f docs: remove "Vanilla JS" highlight from README (#656)
    • 917d1d2 refactor: replace deprecated String.prototype.substr() (#646)
    • 020801a chore: add changelog for version 3.6.0
    • ed1d6f9 test: make test script work on Windows (#643)
    • Additional commits viewable in compare view

    Updates browser-sync from 2.26.7 to 2.27.10

    Release notes

    Sourced from browser-sync's releases.

    2.27.9

    What's Changed

    A bug prevented the help output from displaying - it was introduced when the CLI parser yargs was updated, and is now fixed :)

    Full Changelog: https://github.com/BrowserSync/browser-sync/compare/v2.27.8...v2.27.9

    2.27.8

    This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

    PR:

    Resolved Issues:

    Thanks to @​lachieh for the original PR, which helped me land this fix

    added snippet: boolean option

    This release adds a feature to address BrowserSync/browser-sync#1882

    Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the new snippet option :)

    browser-sync . --no-snippet
    

    or in any Browsersync configuration

    const config = {
      snippet: false,
    };
    

    the original request was related to Eleventy usage, so here's how that would look

    eleventyConfig.setBrowserSyncConfig({
      snippet: false,
    });
    

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump loader-utils and html-webpack-plugin

    Bump loader-utils and html-webpack-plugin

    Bumps loader-utils to 1.4.2 and updates ancestor dependencies loader-utils, loader-utils and html-webpack-plugin. These dependencies need to be updated together.

    Updates loader-utils from 1.1.0 to 1.4.2

    Release notes

    Sourced from loader-utils's releases.

    v1.4.2

    1.4.2 (2022-11-11)

    Bug Fixes

    v1.4.1

    1.4.1 (2022-11-07)

    Bug Fixes

    v1.4.0

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    v1.3.0

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)

    v1.2.3

    1.2.3 (2018-12-27)

    Bug Fixes

    • interpolateName: don't interpolated hashType without hash or contenthash (#140) (3528fd9)

    v1.2.2

    1.2.2 (2018-12-27)

    Bug Fixes

    ... (truncated)

    Changelog

    Sourced from loader-utils's changelog.

    1.4.2 (2022-11-11)

    Bug Fixes

    1.4.1 (2022-11-07)

    Bug Fixes

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)

    1.2.3 (2018-12-27)

    Bug Fixes

    • interpolateName: don't interpolated hashType without hash or contenthash (#140) (3528fd9)

    1.2.2 (2018-12-27)

    Bug Fixes

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for loader-utils since your current version.


    Updates loader-utils from 1.2.3 to 1.4.2

    Release notes

    Sourced from loader-utils's releases.

    v1.4.2

    1.4.2 (2022-11-11)

    Bug Fixes

    v1.4.1

    1.4.1 (2022-11-07)

    Bug Fixes

    v1.4.0

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    v1.3.0

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)

    v1.2.3

    1.2.3 (2018-12-27)

    Bug Fixes

    • interpolateName: don't interpolated hashType without hash or contenthash (#140) (3528fd9)

    v1.2.2

    1.2.2 (2018-12-27)

    Bug Fixes

    ... (truncated)

    Changelog

    Sourced from loader-utils's changelog.

    1.4.2 (2022-11-11)

    Bug Fixes

    1.4.1 (2022-11-07)

    Bug Fixes

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)

    1.2.3 (2018-12-27)

    Bug Fixes

    • interpolateName: don't interpolated hashType without hash or contenthash (#140) (3528fd9)

    1.2.2 (2018-12-27)

    Bug Fixes

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for loader-utils since your current version.


    Updates html-webpack-plugin from 3.2.0 to 5.5.0

    Changelog

    Sourced from html-webpack-plugin's changelog.

    5.5.0 (2021-10-25)

    Features

    • Support type=module via scriptLoading option (1e42625), closes #1663

    5.4.0 (2021-10-15)

    Features

    5.3.2 (2021-06-22)

    Bug Fixes

    • update lodash and pretty error (9c7fba0

    5.3.1 (2021-03-09)

    Bug Fixes

    • remove loader-utils from plugin core (82d0ee8)

    5.3.0 (2021-03-07)

    Features

    • allow to modify the interpolation options in webpack config (d654f5b)
    • drop loader-utils dependency (41d7a50)

    5.2.0 (2021-02-19)

    Features

    5.1.0 (2021-02-12)

    Features

    • omit html tag attribute with null/undefined/false value (aa6e78d), closes #1598

    5.0.0 (2021-02-03)

    ... (truncated)

    Commits
    • 873d75b chore(release): 5.5.0
    • ddeb774 chore: update examples
    • 1e42625 feat: Support type=module via scriptLoading option
    • 7d3645b Bump pretty-error to 4.0.0 to fix transitive vuln for ansi-regex CVE-2021-3807
    • 79be779 [chore] changes actions to run on pull_requests
    • b7e5859 [chore] fixes CI to avoid race conditions
    • 48131d3 chore(release): 5.4.0
    • 16a841a [chore] rebuild examples
    • 3bb7c17 Update index.js
    • e38ac97 Update index.js
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by jantimon, a new releaser for html-webpack-plugin since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
Releases(7.0)
  • 7.0(Sep 3, 2017)

    Breaking Changes

    • Upgraded to React Router 4 #393
    • Upgraded to Webpack 3 #444
    • Upgraded to React Hot Loader 3 #392
    • Upgraded all other dependencies to latest #444 #390 #401
    • Switched to babel-preset-env #411

    Bug fixes

    • Update Jest config to properly handle static assets #457
    • Enhance babel env config to transpile for IE9+ #452
    • Remove escape chars in setupPrompts.js causing linting to fail #449
    • Add jest-cli as an explicit dependency a5cf0e0
    • Copy favicon to /dist #424
    • Switch from open to opn to resolve issue on Windows #421
    • Resolve setup script issues #416

    Enhancements

    • Added prop-types and updated all example code #418
    • Eliminated .babelrc and .eslintrc by moving Babel and ESLint configs to package.json #405

    Documentation

    • Documented more items to check if you receive lint or build errors #151
    • Documented how to configure the public path #415
    Source code(tar.gz)
    Source code(zip)
  • 6.0(Feb 10, 2017)

    Major Enhancements

    Thanks so much to the many contributors that made 6.0 possible!

    Source code(tar.gz)
    Source code(zip)
  • 5.0(Jul 11, 2016)

    v5.0 (2016-07-11)

    Full Changelog

    Another major release with tons of tweaks and improvements! Thanks to everyone for contributing!

    Major Enhancements:

    • Added setup script - Pompts you for initial setup preferences, populates package.json, and runs install. Thanks @gargrave!
    • ES6 Code coverage reporting - Uses Isparta to show code coverage on your ES6 code. Thanks @dwmkerr! View on the command line via npm run test:cover. Open detailed coverage in browser via npm run open:cover.
    • Hash bundles in production build - This supports cache busting. Also generating index.html via html-wepack-plugin so hashed filenames are referenced automatically and HTML is automatically minified. This eliminated the build:html script from package.json.
    • Updated all dependencies to latest versions including React. - Also added react-router-redux.

    Full Change Log

    Implemented enhancements:

    • Hash bundle name #171
    • Create Setup command #148
    • Consider adding react-router-redux #122
    • Add babel-based code coverage #108
    • Add code coverage reporting #97
    • Absolute styles.css path for multi-level paths #143 (rndstr)
    • Added Support for ES6 Coverage #142 (dwmkerr)

    Fixed bugs:

    • npm run lint throws error when spaces are in path on Windows #150
    • Load styles last for same behaviour as in dev mode #144 (rndstr)

    Closed issues:

    • image map require error #191
    • App will not display after build #186
    • Object spread assignment does not work #178
    • Stage1/2 #177
    • Does the webpack prod build exclude all spec.js files from bundle.js? #176
    • Eslint issue #175
    • npm run build error #170
    • CSS in the dev vs prod builds #169
    • Unhandled 'error' event #167
    • Cannot import extract-text-webpack-plugin #164
    • Changed port #159
    • Add carte-blanche #158
    • Instructions for deleting example files missing #145
    • Nested routes are not working when URL is refreshed #65

    Merged pull requests:

    Source code(tar.gz)
    Source code(zip)
  • v4.0(May 13, 2016)

    Another big release - over 100 commits since 3.0! Thanks to everyone for all the PR's!

    Significant changes:

    Implemented enhancements:

    • Add npm script to remove demo #134
    • Eliminate babel-eslint and disable stage-1 support? #87
    • Enhance linting using airbnb's ESLint rules #35

    Fixed bugs:

    • Production build did not work in Android native browser #90

    Closed issues:

    • Now running tests as part of npm run build
    • Adding images to /dist #139
    • Importing images? #138
    • ERROR in %1 is not a valid Win32 application. ?\F:\project\reactjs\react-slingshot\node_modules\node-sass\vendor\win32-x64-47\binding.node @ ./src/styles/styles.scss 4:14-143 13:2-17:4 14:20-149 #136
    • getInitialState #135
    • npm run build !error #133
    • Server Side Rendering #131
      1. should contain : TypeError: Cannot read property 'props' of undefined #130
    • How to add favicon to /dist? #128
    • Adding decorator possibilities #126
    • Support for fonts ttf, eot and woff. problem with the way that URLs are resolved by Chrome when they're parsed from a dynamically loaded CSS blob #124
    • Cannot resolve module [that exists]... #118
    • npm install failure #116
    • Get error when execute "npm start" command. #114
    • Strange issue with react-slingshot #112
    • Using images with slingshot example #106
    • mocha: 'npm start' stops if no .spec.js files in src/ #105
    • Use proptypes-parser for cleaner PropTypes. #104
    • tests throw error when loading images in components #102
    • Database support #101
    • Upgrade to react 15.0 #100
    • How to use in production - NodeJS #99
    • npm install freezes at node-sass and can't run npm start #98
    • Using react-redux-form and redux-thunk #95
    • How to hide a lot of console output? Also for page reload doesn't properly work? #94
    • npm run build error, can't build the files #92

    Merged pull requests:

    • Fixed some spec files being ignored #141 (rndstr)
    • Added .scss as excluded feature for tests #140 (rndstr)
    • Escape dot in webpack file extension regex match #137 (rndstr)
    • Don't use no-unused-vars:0 and jsx-uses-vars:1 together #132 (roburidge)
    • Copy favicon.ico asset to the /dist directory during build #129 (jforaker)
    • Remove unnecessary path to node executables #127 (adam-beck)
    • Support for fonts ttf, eot and woff. problem with the way that URLs a re resolved by Chrome when they're parsed from a dynamically loaded CSS blob #125 (iLeonelPerea)
    • Add babel-register as dev dependency #117 (piotrkaczmarek)
    • Move "connect-history-api-fallback" to devDependencies #115 (nhducit)
    • fix indent issues #111 (vdclouis)
    • fix trackJS message #110 (vdclouis)
    • fix typo #109 (vdclouis)
    • Implements new testing utilities and additional test cases #103 (jeremyadavis)
    Source code(tar.gz)
    Source code(zip)
  • v3.0.1(Mar 31, 2016)

    This is a big release with tons of nice tweaks and fixes. Thanks to everyone for contributing!

    This is 3.0.1 because a few minor changes were missing in the 3.0.0 release.

    Full Changelog

    Implemented enhancements:

    Fixed bugs:

    Closed issues:

    • npm install error #83
    • integration with bootstrap #70
    • SyntaxError: Unexpected keyword 'const'. Const declarations are not supported in strict mode. #67
    • Nested routes are not working when URL is refreshed #65
    • How to run production server #64

    Merged pull requests:

    Source code(tar.gz)
    Source code(zip)
  • v3.0.0(Mar 31, 2016)

  • v2.0.0(Mar 2, 2016)

    React Router is now part of the starter kit! I was very hesitant, but after many conversations, I've decided it's likely to be used more often than not, and it's easier to remove than to add. The Readme includes instructions on how to remove it if you don't want it (and in a future release, I want to automate the process of including/excluding Redux and React Router and their associated configs).

    Closed issues:

    • Upgrade to ESLint 2.0 #54

    Merged pull requests:

    • Adding react-router support. #61 (atfzl)

    Other changes

    • Refactored example app to utilize stateless functional components, destructuring, and honor the concept of container components. Also now generating separate stores for dev and prod to avoid adding hot reloading related cruft to prod code.
    Source code(tar.gz)
    Source code(zip)
  • v1.2.0(Feb 22, 2016)

    v1.2.0 (2016-02-22)

    Full Changelog

    Closed issues:

    • How to enable pushState support? #46
    • Upgrade build tools code to use ES6 #36
    • Errors when trying to import third party plugin. #53
    • Upgrade Redux Thunk #52
    • React-Router #50
    • Add support for including third party modules #48
    • TypeScript support #44
    • @import in css files loaded via webpack results in "File to import not found or unreadable" #43

    Merged pull requests:

    Source code(tar.gz)
    Source code(zip)
  • v1.1.1(Feb 2, 2016)

  • v1.1.0(Feb 1, 2016)

    Generating separate CSS file for prod build. This resolves a flash of unstyled content. In dev, styles continue to be loaded via JavaScript to support hot reloading. More info here.

    Closed issues:

    • Inaccurate Instructions for Removal of Redux #32
    • Bundled scss: flash of unstyled content (FOUC) in chrome #37
    Source code(tar.gz)
    Source code(zip)
  • v1.0.4(Jan 28, 2016)

  • v1.0.2(Jan 21, 2016)

    Full Changelog

    Updated all dependencies to the latest available version (holding off on upgrading to Babel 6 until ESLint support goes out of Beta)

    Closed issues:

    • Update non-pure components to pure components #23
    • Update eslint no-console error level #22
    • Breakpoints not getting hit on initial page load in Chrome Dev Tools #19
    • Port in use error #17
    • No open-coverage script in package.json #12
    • Why BrowserSync over Webpack-dev-server? #11
    • Symbol is not defined #9
    • Unhandled 'error' event on Ubuntu 15.10 #6
    • Run tests as part of build step #1

    Merged pull requests:

    Source code(tar.gz)
    Source code(zip)
  • v1.0.1(Jan 21, 2016)

Owner
Cory House
Principal reactjsconsulting.com, Pluralsight Author, Software Architect
Cory House
Minimal Electron Starter Kit built with Typescript, React, Webpack 5 and Babel 7

electron-webpack-boilerplate Minimal Electron Starter Kit built with Typescript, React, Webpack 5 and Babel 7 To create a JS library, check out js-lib

Francisco Hodge 10 Aug 16, 2022
🚀 A well-structured boilerplate and Starter for Next.js 12+, Tailwind CSS 3, Redux, Redux Thunk, and TypeScript

?? A well-structured boilerplate and Starter for Next.js 12+, Tailwind CSS 3, Redux, Redux Thunk, and TypeScript ⚡️ Made with developer experience first ESLint + Prettier + Lint-Staged + VSCode setup

null 4 Nov 28, 2022
React Native Boilerplate - The Boilerplate contains all the basic packages, common components and, prebuilt code architecture

The Boilerplate contains all the basic packages, common components and, prebuilt code architecture. It will save developer's project setup time.

MindInventory 36 Dec 26, 2022
Next Boilerplate with TypeScript, Redux Toolkit and Styled-Component.. For now

This is a Next.js project bootstrapped with create-next-app. Getting Started First, run the development server: npm run dev # or yarn dev Open http://

Ibrahim Yaacob 2 Feb 17, 2022
IDE and toolkit for building scalable web applications with React, Redux and React-router

An all-in-one solution for creating modern React apps Rekit is a toolkit for building scalable web applications with React, Redux and React-router. It

Rekit 4.5k Jan 2, 2023
Solana Boilerplate - Lightweight boilerplate for Solana dapps. Allows quick building and prototyping.

Lightweight boilerplate for Solana dapps. Allows quick building and prototyping. Feel free to contribute or fork this repository. Make it yours! Leave us a ⭐️ if this repo helped you.

null 21 Nov 15, 2022
NextJS Starter Example for Running Zesty.io CMS

Zesty.io + NextJS Getting Started Node and NPM need to be installed. From your command line.

Zesty.io 9 Dec 8, 2022
A full-stack dApp starter built on Ethereum (Solidity) with Next.js (React).

A full stack dApp starter built on Ethereum (Solidity) with Next.js (React) This repo contains boilerplate code for interacting with a simple smart co

Tom Hirst 272 Dec 30, 2022
Hi there! This is a react native starter which used to build a awesome Event Booking App based on the Figma design. You can download or clone it to speed up your projects.

mcrn-event-booking-app-starter Hi there! This is a react native starter which used to build a awesome Event Booking App based on the Figma design. You

Roy Chen 43 Dec 19, 2022
Teaching boilerplate for teachers that are learning how to program with React

React course: react4teachers-zero2hero Teaching boilerplate for teachers that are learning how to program with React. Course offered by Conselleria d'

Alberto Soto 2 Jun 6, 2022
The official, opinionated, batteries-included toolset for efficient Redux development

Redux Toolkit The official, opinionated, batteries-included toolset for efficient Redux development (Formerly known as "Redux Starter Kit") Installati

Redux 9k Jan 8, 2023
An embedded app starter template with all the required stuff hooked up.

Shopify Node.js x Express.js x React.js Boilerplate An embedded app starter template to get up and ready with Shopify app development with JavaScript.

Harshdeep Singh Hura 124 Dec 25, 2022
An embedded app starter template with all the required stuff hooked up.

Shopify Node.js x Express.js x React.js Boilerplate An embedded app starter template to get up and ready with Shopify app development with JavaScript.

Harshdeep Singh Hura 47 May 25, 2022
An upgradable boilerplate for Progressive web applications (PWA) with server side rendering, build with SEO in mind and achieving max page speed and optimized user experience.

React PWA v2 A highly scalable, Progressive Web Application foundation,boilerplate, with the best Developer Experience. Demo: https://demo.reactpwa.co

Atyantik 2.5k Dec 26, 2022
A default Next.js project with boilerplate packages and configurations. Includes Tailwind, TypeScript (strict), ESLint, Prettier, and Husky.

Yet another Next.js project template This template includes a set of our favorite dev tools scaffolded into a Next.js project. Tools include: TypeScri

Joey McKenzie 16 Dec 27, 2022
A boilerplate for building production-ready RESTful APIs using Node.js, Express, and Mongoose

By running a single command, you will get a production-ready Node.js app installed and fully configured on your machine. The app comes with many built-in features, such as authentication using JWT, request validation, unit and integration tests, continuous integration, docker support, API documentation, pagination, etc. For more details, check the features list below.

Hagop Jamkojian 5k Dec 31, 2022
NextJS, TypeScript and Styled Components project boilerplate

This is a Next.js project bootstrapped with create-next-app. Getting Started First, run the development server: npm run dev # or yarn dev Open http://

Mateus 2 Sep 21, 2021
Boilerplate for HTML, CSS, JS and TailwindCSS

tailwind-vanillajs-boilerplate ?? Boilerplate for HTML, CSS, JS and TailwindCSS

Manu Arora 5 Aug 10, 2022
Next Boilerplate was created to be a template for starting NextJS projects with pre-configured settings like Linters, Test Setup, Storybook and Commit Hooks.

Next Boilerplate was created to be a template for starting NextJS projects with pre-configured settings like Linters, Test Setup, Storybook and Commit Hooks.

Claudio Orlandi 4 Feb 22, 2022