mirror of
https://github.com/google/blockly.git
synced 2026-01-06 16:40:07 +01:00
db70be2c96
* Bump @types/inquirer to version that resolves type errors. * Add types: [] directive to tsconfig.json's compilerOptions to prevent future issues of this kind. See https://github.com/google/blockly/pull/6564#issuecomment-1291885382 for details.
44 lines
1.5 KiB
JSON
44 lines
1.5 KiB
JSON
{
|
|
"include": [
|
|
"core/**/*", // N.B.: also pulls in closure/goog/goog.js if needed.
|
|
"closure/**/*", // Just for ouptut directory structure.
|
|
],
|
|
"exclude": [
|
|
"core/blockly.js"
|
|
],
|
|
"compilerOptions": {
|
|
// Tells TypeScript to read JS files, as
|
|
// normally they are ignored as source files
|
|
"allowJs": true,
|
|
|
|
// Generate d.ts files and sourcemaps.
|
|
"declaration": true,
|
|
// Generate declaration maps used for api-extractor
|
|
"declarationMap": true,
|
|
"sourceMap": true,
|
|
|
|
"module": "ES2015",
|
|
"moduleResolution": "node",
|
|
"target": "ES2020",
|
|
"strict": true,
|
|
|
|
// This does not understand enums only used to define other enums, so we
|
|
// cannot leave it enabled.
|
|
// See: https://github.com/microsoft/TypeScript/issues/49974
|
|
// "importsNotUsedAsValues": "error"
|
|
|
|
// tsc has a clever and usually helpful feature ("@types support")
|
|
// wherein it automatically ingests any type definitions found in
|
|
// node_modues/@types/**/*.d.ts. This lets you tell it about the
|
|
// types for your favourite framework or library just by
|
|
// installing the relevant @types/<whatever> npm package.
|
|
//
|
|
// We don't (as of this writing) use this feature, and it causes a
|
|
// problem when one of our dependencies pulls in such a package
|
|
// which turns out to have syntax errors (see e.g. discussion on
|
|
// PR #6564: https://github.com/google/blockly/pull/6564), so
|
|
// disable it except for the explicitly-specified types.
|
|
"types": [],
|
|
}
|
|
}
|