cc1e5196dd
The idea here is to mirror project templates from our monorepo to the corresponding "top level" repos in our organisation. The main benefits are: - being able to easily synchronise template versions to the last release on release - being able to test those templates together with the rest of the project - being able to deploy the unreleased version of the templates However, this PR will only do the synchronisation part. The main roadblock for the latter at the moment is running `yarn install` on packages in the current `main` that are still unreleased. There are ways around that, but this PR is deliberately minimalistic to land it sooner. ### Change Type - [x] `internal` — Any other changes that don't affect the published package --------- Co-authored-by: Taha <98838967+Taha-Hassan-Git@users.noreply.github.com>
28 lines
589 B
JSON
28 lines
589 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,
|
|
"plugins": [
|
|
{
|
|
"name": "next"
|
|
}
|
|
],
|
|
"paths": {
|
|
"@/*": ["./src/*"]
|
|
}
|
|
},
|
|
"include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
|
|
"exclude": ["node_modules"]
|
|
}
|