Skip to content

fix: use a relative tsconfig root for the TypeScript checker #25209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ZheSun88 merged 1 commit into from
Aug 13, 2026
Merged

fix: use a relative tsconfig root for the TypeScript checker #25209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion flow-server/src/main/resources/vite.generated.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -686,7 +686,12 @@ export const vaadinConfig: UserConfigFn = (env) => {
// exposes the compiler API to Node, so the checker falls back to
// running tsc as a separate process and resolves the config
// strictly against this root without searching parent folders.
root: __dirname
// The root is relative because the checker passes it to tsc as
// "-p <root>" in a command line that is split on spaces, which
// would break for a project directory containing a space. Vite is
// always spawned with the project root as its working directory,
// which is this directory, so "." resolves to the same tsconfig.
root: '.'
}
}),
productionMode && visualizer({ brotliSize: true, filename: bundleSizeFile })
Expand Down
Loading