29550317f7
This prevents it complaining about a missing React import. Enabling this is recommended by the vite starter itself: > Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and add `plugin:react/recommended` & `plugin:react/jsx-runtime` to the `extends` list |
||
|---|---|---|
| .. | ||
| .eslintrc.js | ||
| eslintrc-base.js | ||
| eslintrc-next.js | ||
| eslintrc-react.js | ||
| eslintrc-vite.js | ||
| package.json | ||
| README.md | ||
| tsconfig-typecheck.json | ||
| tsconfig-vite.json | ||
| tsconfig-vite.node.json | ||
@/build-config
Build time configuration files. This can be thought of as a devDependency that
exports various config files that our packages use at build time.
Packaging
This is not a TypeScript package, nor is it linted. It is not meant to be transpiled, it just exports static files that can be included verbatim.
Debugging
Too see what tsc is seeing (say when it is trying to type-check @/utils), use
yarn workspace @/utils tsc --showConfig.
Similarly, to verify what ESLint is trying to do, use
yarn workspace @/utils eslint --debug .
If the issue is in VSCode, open the output window of the corresponding plugin, it might be telling us what's going wrong there. In particular, when changing the settings here, you might need to "Developer: Reload Window" in VSCode to get it to pick up the changes.