Go to file
john dce439f10d 🐞 fix: 2024-07-18 14:39:17 +08:00
.yarn feat: 2024-07-17 13:06:45 +08:00
public feat: 2024-07-16 17:53:55 +08:00
src 🐞 fix: 2024-07-18 14:39:17 +08:00
.env.development feat: 2024-07-16 17:53:55 +08:00
.env.production 🐞 fix: 2024-07-18 14:39:17 +08:00
.eslintrc.cjs feat: 2024-07-16 09:58:31 +08:00
.gitignore feat: 2024-07-16 09:58:31 +08:00
.yarnrc.yml feat: 2024-07-16 09:58:31 +08:00
README.md feat: 2024-07-16 09:58:31 +08:00
iconfont.json feat: 2024-07-17 13:06:45 +08:00
index.html feat: 2024-07-16 17:53:55 +08:00
package-lock.json feat: 2024-07-16 09:58:31 +08:00
package.json feat: 2024-07-17 13:06:45 +08:00
postcss.config.js feat: 2024-07-16 09:58:31 +08:00
tsconfig.json feat: 2024-07-16 09:58:31 +08:00
tsconfig.node.json feat: 2024-07-16 09:58:31 +08:00
tsconfig.node.tsbuildinfo feat: 2024-07-16 17:53:55 +08:00
vite.config.d.ts feat: 2024-07-16 17:53:55 +08:00
vite.config.js feat: 2024-07-16 17:53:55 +08:00
vite.config.ts feat: 2024-07-16 09:58:31 +08:00
yarn.lock feat: 2024-07-17 13:06:45 +08:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

  • Configure the top-level parserOptions property like this:
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
  },
}
  • Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@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-runtime to the extends list