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:
parserOptions: {
ecmaVersion: 'latest',
sourceType: 'module',
project: ['./tsconfig.json', './tsconfig.node.json'],
tsconfigRootDir: __dirname,
},- Replace
plugin:@typescript-eslint/recommendedtoplugin:@typescript-eslint/recommended-type-checkedorplugin:@typescript-eslint/strict-type-checked - Optionally add
plugin:@typescript-eslint/stylistic-type-checked - Install eslint-plugin-react and add
plugin:react/recommended&plugin:react/jsx-runtimeto theextendslist
This section is only required for the initial deployment of this website and is currently maintained for historical documentation. A few steps need to be manually carried out in order to fully provision this static website.
This project includes the files necessary to create preliminary resources before deploying the static web app and other auxiliary resources.
- Manually run a Bicep deployment using .github/bicep/setup.bicep. Open the deployment overview page in a browser.
- From the GitHub repository, go to Settings → Environments, and create a new environment with the name prod. Create the following environment secrets:
- AZURE_CLIENT_ID: ID of the
id-computost-website-deployment-servicemanaged identity - AZURE_SUBSCRIPTION_ID: Can be found from the overview of the managed identity
- AZURE_TENANT_ID: Can be found from the JSON view of the managed identity
- AZURE_CLIENT_ID: ID of the
Currently, end-to-end automation for creating custom domains for Static Web Apps is unsupported. After the site is provisioned, manually carry out the steps described in the articles below: