2020-04-30 23:13:16 +03:00
|
|
|
{
|
|
|
|
|
"compilerOptions": {
|
2020-05-24 18:37:04 +03:00
|
|
|
"target": "es5",
|
|
|
|
|
"module": "esnext",
|
|
|
|
|
"composite": true,
|
|
|
|
|
"strict": true,
|
|
|
|
|
"jsx": "preserve",
|
|
|
|
|
"importHelpers": true,
|
|
|
|
|
"downlevelIteration": true,
|
|
|
|
|
"moduleResolution": "node",
|
|
|
|
|
"experimentalDecorators": true,
|
|
|
|
|
"esModuleInterop": true,
|
|
|
|
|
"allowSyntheticDefaultImports": true,
|
|
|
|
|
"sourceMap": true,
|
|
|
|
|
"outDir": "dist",
|
2020-05-07 00:08:27 +03:00
|
|
|
"lib": [
|
|
|
|
|
"dom",
|
|
|
|
|
"dom.iterable",
|
2022-10-05 19:09:31 +03:00
|
|
|
"es2017"
|
2020-05-24 18:37:04 +03:00
|
|
|
]
|
2020-04-30 23:13:16 +03:00
|
|
|
},
|
Attempt to homogenize and simplify `tsconfig.json` files
I needed to futz with these to get local builds working, and in the
process it looks like we can refine things. In particular:
- We should be able to avoid defining `baseUrl`, `rootDir`, and `paths`
in most cases.
- I've added TypeScript "project references" (`"references"` section)
because that appears to be what you're supposed to do in a monorepo
setup. However, since we're not driving builds with a top-level `tsc`
command, I'm not sure if this is actually buying us anything.
- I've significantly changed the `research-app-messages` config file
to have the same structure as the other projects. It was quite
different, I think just because it was imported later from my
research-app pilot work.
- However, in `engine-pinia` I need to set the TS "rootDir" to `..` to
prevent build errors relating to input file paths. I think that this
might be related to the use of `vue-cli-service` for the build? I
was hoping that the use of the project references would make this
go away, but no such luck.
- And in `research-app-messages` I need to set the TS "rootDir" to `src`
because otherwise the `research-app` build will fail with a complaint
that the module cannot be found. I cannot figure out what's causing
this, or why it's not a problem for other packages such as `astro`.
- In `tests`, we need to keep the `baseUrl` setting because there are
some relative imports that don't use the `./` prefix syntax. It would
be pretty easy to fix this, I believe.
2022-11-29 02:05:00 +03:00
|
|
|
"references": [
|
|
|
|
|
{
|
|
|
|
|
"path": "../embed-common"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"path": "../engine"
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"path": "../engine-pinia"
|
|
|
|
|
}
|
|
|
|
|
],
|
2020-04-30 23:13:16 +03:00
|
|
|
"include": [
|
|
|
|
|
"src/**/*.ts",
|
|
|
|
|
"src/**/*.vue"
|
|
|
|
|
]
|
Attempt to homogenize and simplify `tsconfig.json` files
I needed to futz with these to get local builds working, and in the
process it looks like we can refine things. In particular:
- We should be able to avoid defining `baseUrl`, `rootDir`, and `paths`
in most cases.
- I've added TypeScript "project references" (`"references"` section)
because that appears to be what you're supposed to do in a monorepo
setup. However, since we're not driving builds with a top-level `tsc`
command, I'm not sure if this is actually buying us anything.
- I've significantly changed the `research-app-messages` config file
to have the same structure as the other projects. It was quite
different, I think just because it was imported later from my
research-app pilot work.
- However, in `engine-pinia` I need to set the TS "rootDir" to `..` to
prevent build errors relating to input file paths. I think that this
might be related to the use of `vue-cli-service` for the build? I
was hoping that the use of the project references would make this
go away, but no such luck.
- And in `research-app-messages` I need to set the TS "rootDir" to `src`
because otherwise the `research-app` build will fail with a complaint
that the module cannot be found. I cannot figure out what's causing
this, or why it's not a problem for other packages such as `astro`.
- In `tests`, we need to keep the `baseUrl` setting because there are
some relative imports that don't use the `./` prefix syntax. It would
be pretty easy to fix this, I believe.
2022-11-29 02:05:00 +03:00
|
|
|
}
|
