f19b12c42e
I had some free time at the end of the week so I investigated the idea of deriving the vercel routing config from the react-router config, then storing the derived vercel route info in a jest snapshot, and then loading the jest snapshot during the build script. Seems to work well! ### Change Type - [x] `internal` — Any other changes that don't affect the published package[^2]
41 lines
783 B
JSON
41 lines
783 B
JSON
{
|
|
"compilerOptions": {
|
|
"target": "es5",
|
|
"lib": ["dom", "dom.iterable", "esnext"],
|
|
"allowJs": true,
|
|
"skipLibCheck": true,
|
|
"strict": true,
|
|
"forceConsistentCasingInFileNames": true,
|
|
"noEmit": true,
|
|
"esModuleInterop": true,
|
|
"module": "esnext",
|
|
"moduleResolution": "node",
|
|
"resolveJsonModule": true,
|
|
"isolatedModules": true,
|
|
"jsx": "preserve",
|
|
"incremental": true,
|
|
"experimentalDecorators": true,
|
|
"downlevelIteration": true,
|
|
"plugins": [
|
|
{
|
|
"name": "next"
|
|
}
|
|
]
|
|
},
|
|
"include": ["**/*.ts", "**/*.tsx"],
|
|
"exclude": ["node_modules", "_archive"],
|
|
"references": [
|
|
{
|
|
"path": "../../packages/assets"
|
|
},
|
|
{
|
|
"path": "../../packages/tldraw"
|
|
},
|
|
{
|
|
"path": "../../packages/tlsync"
|
|
},
|
|
{
|
|
"path": "../../packages/validate"
|
|
}
|
|
]
|
|
}
|