This project was bootstrapped with Create React App.

Project has been bootstrapped with: Node v12.18.2, npm 6.14.5, yarn 1.22.4 (Recommended versions are: Node >= 8.10, npm >= 5.6, yarn >= 1.22)

This project uses Yarn for scripting, package management and upgrades. Please do not use npm.

In the project directory, you can run:

Install dependencies before first 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.

Builds the app for production to the build folder.
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.

Upgrade dependencies to the latest versions

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.

• Create branch for the new change (free naming)
• Create Pull request once changes are finished and all tests succeessfully run
• Alternatively, create a draft pull request
• Pull request description must be informative (it is used further down the track to understand changes)
• Merge pull request (no review process at the moment)

NB: very small changes can go without PRs at the moment