This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
-
Configure the top-level
parserOptionsproperty like this:export default tseslint.config({ languageOptions: { // other options... parserOptions: { project: ['./tsconfig.node.json', './tsconfig.app.json'], tsconfigRootDir: import.meta.dirname, }, }, })
-
Replace
tseslint.configs.recommendedwithtseslint.configs.recommendedTypeCheckedortseslint.configs.strictTypeChecked -
Optionally add
...tseslint.configs.stylisticTypeChecked -
Install eslint-plugin-react and update the config:
// eslint.config.js import react from 'eslint-plugin-react' export default tseslint.config({ // Set the react version settings: { react: { version: '18.3' } }, plugins: { // Add the react plugin react, }, rules: { // other rules... // Enable its recommended rules ...react.configs.recommended.rules, ...react.configs['jsx-runtime'].rules, }, })
To enable CI/CD for automatic deployment, add the following secrets in the GitHub Secrets settings of your repository or organization:
DOCKER_USERNAME– your Docker registry usernameDOCKER_PASSWORD– your Docker registry passwordWATCHTOWER_HTTP_API_TOKEN– the API token for secure Watchtower API accessWATCHTOWER_UPDATE_ENDPOINT– the endpoint for the Watchtower production updateWATCHTOWER_UPDATE_ENDPOINT_DEV– the endpoint for the Watchtower development update
The Docker image name is automatically set to the name of the repository. If the repository name changes, a new Docker image will be created in the Docker registry with the new name.