vscode/extensions/shared.tsconfig.json

{
	"compilerOptions": {
		"target": "es2018",
		"lib": [
			"es2018"
		],
		"module": "commonjs",
		"strict": true,
		"alwaysStrict": true,
		"noImplicitAny": true,
		"noImplicitReturns": true,
		"noUnusedLocals": true,
		"noUnusedParameters": true
	}
}
Introduce a shared tsconfig for extensions Setup a baseline tsconfig for extensions to extend. This will help make sure thatof our built-in extensions are using the recommended settings for target and so on. it also reduces duplicated code and will make updating tsconfig settings easier 2018-10-02 01:35:43 +02:00			`{`
			`"compilerOptions": {`
Use 2018 as target for extensions since we are now running on node 10 2019-02-21 01:09:25 +01:00			`"target": "es2018",`
Don't include dom typings in extensions (#89942) Problem All of our extensions currently are built using the dom typings. This can lead to runtime errors if you mistakenly use `window` or similar Fix Exclude the dom typings from compile. Then explicitly import the node types for `URL` and `TextEncoder` 2020-02-04 20:08:22 +01:00			`"lib": [`
			`"es2018"`
			`],`
Introduce a shared tsconfig for extensions Setup a baseline tsconfig for extensions to extend. This will help make sure thatof our built-in extensions are using the recommended settings for target and so on. it also reduces duplicated code and will make updating tsconfig settings easier 2018-10-02 01:35:43 +02:00			`"module": "commonjs",`
			`"strict": true,`
			`"alwaysStrict": true,`
			`"noImplicitAny": true,`
			`"noImplicitReturns": true,`
			`"noUnusedLocals": true,`
			`"noUnusedParameters": true`
			`}`
Don't include dom typings in extensions (#89942) Problem All of our extensions currently are built using the dom typings. This can lead to runtime errors if you mistakenly use `window` or similar Fix Exclude the dom typings from compile. Then explicitly import the node types for `URL` and `TextEncoder` 2020-02-04 20:08:22 +01:00			`}`