fcc36ac908
* Make astro package play nice with node16 module resolution Projects using node16 module resolution in typescript uses the new exports and imports configuration from typescript to find definition files. This mirrors how nodejs resolves the files. If a package contains an exports map in the package.json, typescript will ignore the "types" field (not sure how it plays with typesVersions). This moves the typings hirearchy of definition files into the same hierarchy that astro produces output files in, so that typescript can discover them. Fixes: #4172 * Add changeset * Reorder export keys * Update paths inside .d.ts files Co-authored-by: Princesseuh <princssdev@gmail.com>
12 lines
259 B
JSON
12 lines
259 B
JSON
{
|
|
"extends": "../../tsconfig.base.json",
|
|
"include": ["src", "index.d.ts"],
|
|
"compilerOptions": {
|
|
"allowJs": true,
|
|
"declarationDir": "./dist",
|
|
"module": "ES2020",
|
|
"outDir": "./dist",
|
|
"target": "ES2020",
|
|
"types": ["./client"]
|
|
}
|
|
}
|