This project was bootstrapped with Create React App.
- リリースビルド
- Router
- ページ間、コンポーネント間の値渡し
- ESLint
- React hook
- Image
- マテリアルデザイン
- ボタン
- スイッチ
- フォーム、テキストフィールド
- アプリバー
- ナビゲーションドロワー
- カード
- 多言語化
- ダークモード
- emotion
- injection
- CSSでゴニョゴニョ
- Redux
- Redux logger
- Firebase連携
- listener周り
- Neumorphism
- カルーセル
- グラフ
- カレンダー
- test
https://react-validation-86b59.web.app/
git clone https://github.com/hukusuke1007/react-validation.git
cd react-validation
yarn
# run
yarn start
# test
yarn jest
俺以外見なくて良い。
npx create-react-app app-name --typescript
cd app-name
yarn eject
To modify webpack.config.js to add ts-loader.
module: {
strictExportPresence: true,
rules: [
// ...
{
// add
oneOf: [
{
test: /\.(js|mjs|jsx|ts|tsx)$/,
include: paths.appSrc,
exclude: /node_modules/,
use: [{
loader: 'ts-loader'
}]
},
// ....
# Design
# https://material-ui.com/ja/getting-started/installation/
yarn add @material-ui/core @material-ui/icons @emotion/core emotion/styled
# Localized
yarn add i18next react-i18next
# DI
yarn add tsyringe reflect-metadata
yarn add ts-loader --dev
# Firebase
yarn add firebase @1amageek/ballcap"
cp dotenvsample .development.env
cp dotenvsample .production.env
{
"compilerOptions": {
"target": "es2018",
"lib": [
"dom",
"dom.iterable",
"esnext",
"es6",
"es2016"
],
"allowJs": true,
"skipLibCheck": true,
"esModuleInterop": true,
"allowSyntheticDefaultImports": true,
"strict": true,
"forceConsistentCasingInFileNames": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": false,
"noEmit": false,
"jsx": "react",
"types": ["jest", "reflect-metadata"],
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
},
"include": [
"src"
]
}
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.