Mastermindzh
5829588665
Added default output to jest (for terminal output...) Upgraded npm packages. Left jest on 27 because of breaking changes in 28 |
||
---|---|---|
.husky | ||
.vscode | ||
config | ||
cypress | ||
public | ||
scripts | ||
src | ||
.babelrc | ||
.browserslistrc | ||
.dockerignore | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc | ||
.gitignore | ||
.nvmrc | ||
.prettierrc.js | ||
CHANGELOG.md | ||
cypress.config.ts | ||
Dockerfile | ||
jest.config.js | ||
package-lock.json | ||
package.json | ||
README.md | ||
tsconfig.json |
react-starter-kit
Web project starter kit including modern tools and workflows based on create-react-app and best practices from the community. Provides a scalable base template and a good learning base. Suitable for enterprise usage
Includes:
- Redux-toolkit
- Vscode setup (debugging + snippets)
- Jest, @testing-library and Cypress
- Immer
Table of contents
Getting started
npm install
npm start
(localhost:3000)npm test
(run jest + coverage on localhost:8080)
Project structure
Only the important files are shown
.
├── .vscode # vscode setup (debug, snippets, etc)
├── config # tool configuration
├── cypress # e2e tests
├── dist # production version
├── public
├── public # directory with public files (config, icons, etc), will be copied to dist
│ ├── i18n # directory to house i18n language files
│ ├── config.js # default runtime application config
│ └── configOverride.js # default config overrides.
├── scripts # Modified default create-react-app scripts
├── src # application source
│ ├── app # redux-toolkit hooks + store
│ └── infrastructure # infrastructure code (wrappers, navigation, config file class)
├── CHANGELOG.md # update this whenever you update the application
├── Dockerfile # Dockerfile to build nginx container
├── jest.config.js # configuration for jest
├── package.json
├── README.md # keep this up to date
└── tsconfig.json
Configuration
This starter kit comes with runtime configuration out-of-the-box.
It achieves this with 2 config files in the public directory: config.js
and configOverrides.js
.
config.js
is meant to be filled with a default for all of your application's runtime configurations.
configOverrides.js
is meant to be replaced during deployment with environment specific runtime overrides.
Using the config.ts
file
To use the config you import Config
from config.ts
and use the typed object:
import { Config } from "../config";
import { FunctionComponent } from "react";
export const Navbar: FunctionComponent<{}> = () => {
return <h1>{JSON.stringify(Config)}</h1>;
};
adding values
To add a value to the runtime config you have to take 2 steps:
-
Add a type to the
RuntimeConfig
type in src/infrastructure/config/RunTimeConfig.tstype RunTimeConfig = { version: number; name: string; myNewKey: string; };
-
Add a key (if required) to [public/config.js]