64231c73f1
Configuration changes taken from the vite starter (react-ts). From the vite docs (https://github.com/vitejs/vite-plugin-react-swc?tab=readme-ov-file#consistent-components-exports) > For React refresh to work correctly, your file should only export React components. > > If an incompatible change in exports is found, the module will be invalidated. > To make it easier to export simple constants alongside your component the module > is only invalidated when their value changes. While we're not currently using vite for our main apps, it would be worthwhile to write code in a way that a future migration to it is painless if needed. About the what and the why, the Gatsby docs are illuminating: https://www.gatsbyjs.com/docs/reference/local-development/fast-refresh/#how-it-works Some other refs: - https://github.com/ArnaudBarre/eslint-plugin-react-refresh - https://github.com/vitejs/vite/discussions/4577#discussioncomment-1161007 - https://github.com/vitejs/vite-plugin-react/issues/34
15 lines
435 B
JSON
15 lines
435 B
JSON
{
|
|
"name": "@/build-config",
|
|
"version": "0.0.0",
|
|
"private": true,
|
|
"devDependencies": {
|
|
"@typescript-eslint/eslint-plugin": "^7",
|
|
"@typescript-eslint/parser": "^7",
|
|
"eslint-plugin-react": "^7.34",
|
|
"eslint-plugin-react-hooks": "^4.6",
|
|
"eslint-plugin-react-refresh": "^0.4.6",
|
|
"prettier-plugin-organize-imports": "^3.2",
|
|
"prettier-plugin-packagejson": "^2.4"
|
|
}
|
|
}
|