Replies: 3 comments
-
any news on this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
i have the same issue |
Beta Was this translation helpful? Give feedback.
0 replies
-
Managed to get it to work by changing my {
"include": ["**/*.ts", "**/*.tsx", ".react-router/types/**/*"],
"compilerOptions": {
"isolatedModules": true,
"jsx": "react-jsx",
"module": "ESNext",
"target": "ESNext",
"moduleResolution": "Bundler",
"resolveJsonModule": true,
"strict": true,
"skipLibCheck": true,
"allowImportingTsExtensions": true,
"noUncheckedIndexedAccess": true,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"baseUrl": ".",
"types": ["@react-router/node", "vite/client"],
"rootDirs": [".", "./.react-router/types"],
"paths": {
"~/*": ["./app/*"]
}
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🙏 Any help or even small pointers would be very much appreciated
Context
My team has recently started to work on a rr7 migration branch of our remix-run application, currently their seems to be issues when it comes to building with vite (
react-router dev
).I will try to provide as much insight into the relevant config but please forgive if I am missing anything that can prove useful for diagnostic.
I have been referencing Upgrading from Remix and seemingly all steps are covered.
Issue
When launching dev server the following error occurs:
I have a few confident assertions:
tree .react-router/types
confirms that there exists generated types for each routeRoute
imports of this pattern (pasting specific example):import {type Route} from './+types/extract-fields'
include
item:".react-router/types/**/*"
intsconfig.json
and does not highlight any errors (thus the file can be assumed to exist)./+types/...
for a given route but mergedConfig
vite.config.ts
tsconfig.json
react-router.config.ts
Package.json
dev
scriptsBeta Was this translation helpful? Give feedback.
All reactions