arrow_back Why React is not suitable for building rich-text editors?
Setting up React project for your team
Submitted by Souvik Basu (@souvikbasu) on Thursday, 7 December 2017
React being a library and not a framework offers us with a lot of choice to create our of own ecosystem. This gives us a lot of power to pick and choose the best libraries that suits our need. But for most of us, it is also a lot of hardwork to create the ecosystem from scratch. In fact, with increasing number of options to choose from for router, state management, type safety, etc., sometimes it gets more and more confusing for us. This workshop is to get you started to create your React project with best practices and most used industry recommended libraries
We will create a React app (ecosystem) that has following items taken care of:
- Create app (React 16) using Create React App cli - Use ESLint for linting and add git hooks - Test using Jest and Enzyme and add to git hooks - Add Server Side Rendering (Universal app) - Use React Router v4 - Use Redux - Add GraphQL and Apollo - Add Docker support - Add Code Splitting - Use React Saga - Enable Hot reloading - Implement Error Handling of React components - Add Logging support - Add Code Coverage tool - Add Styling support - Add NotFound and Error components and routes - Add Analytics - Add support for Responsiveness - Add Type Safety
Laptop with latest node installed
Souvik is a JS enthusiasts with 14 years experience in the industry. His day job is to set up a team on React project in Tesco Bengaluru. He loves to code equally well in React as well as in Angular. Currently he is spending a lot of time exploring Conversational UI.