Files
coder/site/tsconfig.json
T
Kayla はな b06d183a32 chore: begin modernizing typescript imports (#23509)
- update some config settings to support "absolute"-style imports by
using a `#/` prefix
- migrate some of the imports in the `WorkspacesPage` to use the new
import style as a proof of concept

because of the change in import sorting behavior this results in, this
diff is already kind of hard to look at–even just from a small migration
for a single page. I think breaking this up into bite size pieces isn't
gonna be worth the work, and leaves more time for merge conflicts to
accrue, more times people would likely have to resolve them.

so I think as far as process for this, I'd like to...

- merge this PR as is, where the config changes are relatively easy to
spot in the haystack, with just enough imports updated to prove that the
config changes are correct
- merge another mega PR after this one which just bites the bullet and
migrates everything else in one fell swoop. it'll probably result in a
ton of merge conflicts for open PRs, but at least it'll only do so once
and then it can be over with.
2026-03-24 11:14:44 -06:00

35 lines
712 B
JSON

{
"compilerOptions": {
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"incremental": true,
"isolatedModules": true,
"jsx": "react-jsx",
"jsxImportSource": "@emotion/react",
"lib": ["dom", "dom.iterable", "esnext"],
"module": "preserve",
"moduleResolution": "bundler",
"noEmit": true,
"outDir": "build/",
"preserveWatchOutput": true,
"resolveJsonModule": true,
"skipLibCheck": true,
"strict": true,
"target": "es2020",
"types": [
"node",
"react",
"react-dom",
"vite/client",
"vitest/globals",
"novnc__novnc"
],
"baseUrl": "src/",
"paths": {
"#/*": ["*"]
}
},
"include": ["**/*.ts", "**/*.tsx"],
"exclude": ["node_modules/"]
}