openmct/tsconfig.json

/* Note: Open MCT does not intend to support the entire Typescript ecosystem at this time.
 * This file is intended to add Intellisense for IDEs like VSCode. For more information
 * about Typescript, please discuss in https://github.com/nasa/openmct/discussions/4693
*/ 
{
    "compilerOptions": {
        "allowJs": true,
        "checkJs": true,
        "strict": true,
        "module": "esnext",
        "moduleResolution": "node"
    }
}
Move off node10 and add intellisense (#4643) * Move off node10 and bring in node16 * Update engine lock * update webpack and add the output.hashFunction option to avoid a potential issue with Node 17 in case the config changes closer to defaults At the moment there is no error with Node 17 because the config strays from the defaults and avoids the common case. Also add a tsconfig.json file that enables VS Code and other IDEs to perform type checking on the side. For example now the webpack config file is type checked. This does not impact any existing processes, our build scripts are left untouched and only IDEs will use it for live intellisense and type checking when viewing files (f.e. showing helpful red squiggly underlines on type errors) * mini-css-extract-plugin * Update webpack.prod.js * Update webpack.prod.js * 15 * Update config.yml * Updated config.yml * Updated config.yml * Updated config.yml * Update package.json * comment and EOF Co-authored-by: Joe Pea <joe.pea@nasa.gov> Co-authored-by: Joe Pea <trusktr@gmail.com> Co-authored-by: Andrew Henry <akhenry@gmail.com> 2022-01-07 11:39:25 -08:00			`/* Note: Open MCT does not intend to support the entire Typescript ecosystem at this time.`
			`* This file is intended to add Intellisense for IDEs like VSCode. For more information`
			`* about Typescript, please discuss in https://github.com/nasa/openmct/discussions/4693`
			`*/`
			`{`
			`"compilerOptions": {`
			`"allowJs": true,`
			`"checkJs": true,`
			`"strict": true,`
			`"module": "esnext",`
			`"moduleResolution": "node"`
			`}`
			`}`