adeelibr / react-starter-kit

React, Redux, Webpack, Material UI, Boostrap 4, Code Splitting, HMR

Documentation

Webapp Was Built In:

• ReactJS
• Redux
• Webpack 4
• Babel 7
• React Material UI
• Bootstrap 4
• SCSS, CSS Support
• HMR
• Code Splitting with React.lazy & React.Suspense
• Code Formatter (Prettier)
• Eslint configured extended with Airbnb style guide & support for prettier
• Jest & Enzyme Configured
• Automatically lint & format code, when committing it. [Husky/Lint-Staged]

Tutorials

Things I did while setting up the boiler plate for this code base, I wrote it all down in a series of articles

• https://medium.freecodecamp.org/how-to-conquer-webpack-4-and-build-a-sweet-react-app-236d721e6745
• https://medium.freecodecamp.org/how-to-combine-webpack-4-and-babel-7-to-create-a-fantastic-react-app-845797e036ff
• https://medium.freecodecamp.org/these-tools-will-help-you-write-clean-code-da4b5401f68e
• https://medium.freecodecamp.org/how-to-set-up-jest-enzyme-like-a-boss-8455a2bc6d56

Deploying a Node Instance On Linux Server Using PM2

How to start on PM2 [This is specific if you serve your files on a linux server where a NodeJS application is deployed as a server serving the .js files

 npm i
 node_modules/.bin/webpack --config webpack.prod.config.js --colors --progress
 node server
 PORT=8082 pm2 start server --name "app-name-to-deploy"

react-starter-kit's Issues

@babel/polyfill package has been deprecated

any upgrade plans for this repo?

small improve

I article is great! Thanks a lot. I did some changes in package json to make it work with
"@babel/core": "^7.8.3".
I move "@babel/polyfill": "^7.8.3" to dependencies and added import "@babel/polyfill"; in index.js.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.