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.
Runs automated code formatting on all applicable file types.
Lints all applicable files and prints the output.
Dry-runs the TypeScript compiler. This is especially useful to check whether any types or references broke after a big refactoring.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Launches Storybook.
Stories are automatically added from all *.stories.tsx files.
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.
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.
First off: All files and directories should be named in lowerCamelCase.ts. The only exception are some-package-name.d.ts files specifying typings for npm packages. There is no exception in casing for files holding a component.
The project is structured in the following way:
.storybook/: Storybook configpublic/: Static files copied over to the buildsrc/: Application sourceapp/: The app's entry pointcomponents/: Components that do not hook into the application storei18n/: Internationalization config and translationslib/: Application-independent library code that could later be extracted into its own packagemodels/: mobx-state-tree modelsscreens/: All screens accessible via their own routestories/: Leave as is, holds configuration for storyshot teststheme/: Shared SCSS like commonly used colors, etc.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.