npm install pro-admin-subapp
How is this project generated
This project is creted using create-react-app
npm install --save-dev @storybook/addon-actions @storybook/addon-knobs @storybook/addon-links @storybook/addon-storyshots @storybook/addons @storybook/react babel-core babel-runtime eslint-config-airbnb eslint-config-prettier eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-prettier eslint-plugin-react prettier react-test-renderer redux-mock-store
Copied .storybook, src/storybook.test.js from sample taskbox project
Exploring alternative to ejecting from create-react-app: https://auth0.com/blog/how-to-configure-create-react-app/
Make sure that the create-react-app is > v2.1.x
Ultimately the forking option did not work out on multiple trails, so finally decided to eject and continue the development.
Executed command npm run eject or yarn eject
npm install --save-dev eslint-loader eslint-plugin-flowtype eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-prettier eslint-plugin-react
In order to split component loading, added npm install --save @loadable/component
In pegasus-web fetch library is used for API calling. However, axios is better than fetch: https://firstname.lastname@example.org/http-requests-compared-why-axios-is-better-than-node-fetch-more-secure-can-handle-errors-better-39fde869a4a6
So created a common Axios API helper.
npm install --save redux-toolbelt redux-toolbelt-saga redux-saga
By default, at root level only public and src folders are created by create-react-app. Inside src folder following structure is implemented: src
Conventions to follow while working on this project
Default generated notes
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you
eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can
eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except
eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use
eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify