Our team utilizes TypeScript with both Atom and VSCode as our editors, but we are facing challenges with the tsconfig.json file.
- VSCode is not recognizing the typings, causing the namespace for 'ng' (for Angular 1.x) to be unknown in VSCode.
- When it comes to the tsconfig.json file, VSCode is commenting it out with the message: 'Matches a schema that is not allowed.'
I suspect there may be a connection between these issues.
{
"compilerOptions":
{
"target": "es5",
"module": "commonjs",
"declaration": false,
"noImplicitAny": false,
"removeComments": true,
"noLib": false,
"preserveConstEnums": true,
"suppressImplicitAnyIndexErrors": true,
"outDir": "./tmp/typescript",
"rootDir": "./our/ts/dir"
},
"filesGlob": [
"./src/**/*.ts",
"!./node_modules/**/*.ts",
"./bower_components/our_library/src/company/**/*.ts",
"./typings/tsd.d.ts"
],
"files": [
"./src/example.ts",
"./src/many/many/entries/any.ts",
"./src/lib.ts/a_library.ts",
"./src/lib.ts/angular.ts",
"./src/lib.ts/jquery.ts",
"./src/lib.ts/lodash.ts",
"./src/lib.ts/moment.ts",
"./src/lib.ts/restangular.ts",
"./src/lib.ts/selectize.ts",
"./src/lib.ts/systemjs.ts",
"./typings/tsd.d.ts"
],
"exclude": [],
"atom": {
"rewriteTsconfig": true
}
}
I have attempted to address the issue following guidance from this resource, but the solution provided did not resolve the problem. Additionally, consulting the tsconfig.json spec did not offer much help either, as the error message persists even when removing the 'filesGlob' and 'atom' fields in the JSON.
We would appreciate any advice or suggestions on how to tackle this issue.