Matchu
567e333f9e
I'm interested in ejecting from Vercel, so I'm trying to get off their proprietary-ish create-react-app + Vercel API thing, and onto Nextjs, which is very similar in shape, but more portable. I had to disable `craCompat` in `next.config.js` to stop us from crashing on their webpack config, see https://github.com/vercel/next.js/discussions/25858#discussioncomment-1573822 The frontend seems to work at a basic level, but network requests fail, and images don't seem to be working. I'll work on those next! Note that this commit was forced through despite failing lint checks. We'll need to fix that up too! Also, after the codemod, I moved `src/pages` to the more canonical location `pages`. Lint tooling seemed surprised to not find a `pages` directory, and I didn't see a config that was making it work correctly in the other location, so I figured it's that Next is willing to check `pages` or `src/pages`? But this is more canonical so yeah!
29 lines
697 B
JSON
29 lines
697 B
JSON
{
|
|
"compilerOptions": {
|
|
"target": "esnext",
|
|
"module": "esnext",
|
|
"downlevelIteration": true,
|
|
"strict": true,
|
|
"esModuleInterop": true,
|
|
"skipLibCheck": true,
|
|
"forceConsistentCasingInFileNames": true,
|
|
"lib": ["dom", "dom.iterable", "esnext"],
|
|
"allowJs": true,
|
|
"allowSyntheticDefaultImports": true,
|
|
"noFallthroughCasesInSwitch": true,
|
|
"moduleResolution": "node",
|
|
"resolveJsonModule": true,
|
|
"isolatedModules": true,
|
|
"noEmit": true,
|
|
"jsx": "preserve",
|
|
"incremental": true
|
|
},
|
|
"ts-node": {
|
|
"compilerOptions": {
|
|
"target": "esnext",
|
|
"module": "commonjs"
|
|
}
|
|
},
|
|
"include": ["src"],
|
|
"exclude": ["node_modules"]
|
|
}
|