Why nextjs.json has duplicates from base.json #1995
-
|
I created a pure turborepo using: npx create-turbo@latestI noticed that the {
"$schema": "https://json.schemastore.org/tsconfig",
"display": "Next.js",
"extends": "./base.json",
"compilerOptions": {
"target": "es5",
"lib": ["dom", "dom.iterable", "esnext"],
"allowJs": true,
"skipLibCheck": true,
"strict": true,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"incremental": true,
"esModuleInterop": true,
"module": "esnext",
"resolveJsonModule": true,
"isolatedModules": true,
"jsx": "preserve"
},
"include": ["src", "next-env.d.ts"],
"exclude": ["node_modules"]
}{
"$schema": "https://json.schemastore.org/tsconfig",
"display": "Default",
"compilerOptions": {
"composite": false,
"declaration": true,
"declarationMap": true,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"inlineSources": false,
"isolatedModules": true,
"moduleResolution": "node",
"noUnusedLocals": false,
"noUnusedParameters": false,
"preserveWatchOutput": true,
"skipLibCheck": true,
"strict": true
},
"exclude": ["node_modules"]
}As we can see, Why is that? It's just a mistake or a kind of convention/feature? |
Beta Was this translation helpful? Give feedback.
Answered by
nathanhammond
Sep 19, 2022
Replies: 1 comment
-
|
This is because these are intended to be used in distinct scenarios. The overlap is intentional so that they're able to clobber and diverge over time. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
nathanhammond
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is because these are intended to be used in distinct scenarios. The overlap is intentional so that they're able to clobber and diverge over time.