vscode/extensions/typescript-language-features/tsconfig.json

{
	"extends": "../tsconfig.base.json",
	"compilerOptions": {
		"outDir": "./out",
		"esModuleInterop": true,
		"experimentalDecorators": true,
		"types": [
			"node"
		]
	},
	"include": [
		"src/**/*",
		"../../src/vscode-dts/vscode.d.ts",
		"../../src/vscode-dts/vscode.proposed.codeActionAI.d.ts",
		"../../src/vscode-dts/vscode.proposed.codeActionRanges.d.ts",
		"../../src/vscode-dts/vscode.proposed.mappedEditsProvider.d.ts",
		"../../src/vscode-dts/vscode.proposed.multiDocumentHighlightProvider.d.ts",
		"../../src/vscode-dts/vscode.proposed.workspaceTrust.d.ts",
	]
}
Fixed line terminators 2016-02-19 17:26:28 +00:00			`{`
Use more standard name for shared extension tsconfig This enables Intellisense in the `tsconfig.base` file 2021-04-12 22:58:38 +00:00			`"extends": "../tsconfig.base.json",`
Fixed line terminators 2016-02-19 17:26:28 +00:00			`"compilerOptions": {`
Use Strict Null Checks In TS Extension (#16244) * Use Strict Null Checks In TS Extension Updates the Ts extension to use strict null checks. * Throw instead of returning undefined in some linkedmap cases * fix small null check in buffersync * Fix for request item null 2016-12-01 21:48:03 +00:00			`"outDir": "./out",`
JS/TS package acquisition (#184438) * Experiment with adding ata using `@types` packages shipped in an extension * Use own file system instead of `https` * JS/TS type support on web * Tsconfig needs esModuleInterop not module:nodenext We actually want webpack to emit commonjs, but need to write ES default imports to use node-maintainer * fix package.json indentation * Adding setting to disable web type acquisition * Fix merge of yarn lock * Fixing merge errors * Fixing errors * Pick up package externally * Fixing conflicts * Bump version --------- Co-authored-by: Kat Marchán <kzm@zkat.tech> Co-authored-by: Nathan Shively-Sanders <293473+sandersn@users.noreply.github.com> 2023-08-28 07:49:40 +00:00			`"esModuleInterop": true,`
Build TS extension against current vscode.d.ts directly Currently extensions like TS have a dev dependency on the `"vscode"` package. This pulls in a copy of `vscode.d.ts` that we end up using instead of our local `vscode.d.ts`. This change uses the `paths` `tsconig` option so that we use our local `vscode.d.ts` instead of the one from `node_modules` 2020-02-04 22:19:16 +00:00			`"experimentalDecorators": true,`
move vscode.d.ts and vscode.proposed.d.ts into `src/vscode-dts`-folder, https://github.com/microsoft/vscode/issues/131165 2021-11-09 14:00:03 +00:00			`"types": [`
			`"node"`
use tsconfig.json#include for vscode.d.ts and vscode.proposed.d.ts, enables to remove most ref.d.ts-files 2021-11-09 14:53:35 +00:00			`]`
Fixed line terminators 2016-02-19 17:26:28 +00:00			`},`
Add "Include" to extension TSConfig Files (#25860) Bug Most VSCode extensions currently specify `"exclude"` in their `tsconfig.json` but not `"include"`. This may result in extra files being included in each project Fix Add `"include": ["src/*/"]` to all extension tsconfig files 2017-05-05 18:37:59 +00:00			`"include": [`
use tsconfig.json#include for vscode.d.ts and vscode.proposed.d.ts, enables to remove most ref.d.ts-files 2021-11-09 14:53:35 +00:00			`"src/*/",`
			`"../../src/vscode-dts/vscode.d.ts",`
Split TS' AI-backed code actions into separate entries (#201140) * Split TS' AI-backed code actions into separate entries Lets the user decide whether to add AI to their code action, which shows intent, which is good for us to learn whether people actually want this. Related: this should be unflagged for insiders. To do this, do I just delete the flags? * Stop appending a duplicate message in missingFunctionDeclaration * Fix: quickfix was still showing Copilot-only It's a workaround--I'm not sure of the right way to do this. * Update to use `isAI` * Put AI code actions after others. * Add isAI to rest of code actions * Remove flags for TS AI code actions * Check for copilot-chat instead of copilot It's possible to have copilot installed without copilot-chat. * Fix file casing --------- Co-authored-by: Matt Bierner <matb@microsoft.com> 2024-01-31 22:46:39 +00:00			`"../../src/vscode-dts/vscode.proposed.codeActionAI.d.ts",`
groundwork for code action ranges for quick fix (#204191) * added in config * fix balance between diagnostic and range * cleanup 2024-02-05 22:13:18 +00:00			`"../../src/vscode-dts/vscode.proposed.codeActionRanges.d.ts",`
Hook up mapped code edits experiment for TS (#198478) For https://github.com/microsoft/TypeScript/pull/55406 2023-11-17 02:07:09 +00:00			`"../../src/vscode-dts/vscode.proposed.mappedEditsProvider.d.ts",`
Split TS' AI-backed code actions into separate entries (#201140) * Split TS' AI-backed code actions into separate entries Lets the user decide whether to add AI to their code action, which shows intent, which is good for us to learn whether people actually want this. Related: this should be unflagged for insiders. To do this, do I just delete the flags? * Stop appending a duplicate message in missingFunctionDeclaration * Fix: quickfix was still showing Copilot-only It's a workaround--I'm not sure of the right way to do this. * Update to use `isAI` * Put AI code actions after others. * Add isAI to rest of code actions * Remove flags for TS AI code actions * Check for copilot-chat instead of copilot It's possible to have copilot installed without copilot-chat. * Fix file casing --------- Co-authored-by: Matt Bierner <matb@microsoft.com> 2024-01-31 22:46:39 +00:00			`"../../src/vscode-dts/vscode.proposed.multiDocumentHighlightProvider.d.ts",`
			`"../../src/vscode-dts/vscode.proposed.workspaceTrust.d.ts",`
Fixed line terminators 2016-02-19 17:26:28 +00:00			`]`
Build TS extension against current vscode.d.ts directly Currently extensions like TS have a dev dependency on the `"vscode"` package. This pulls in a copy of `vscode.d.ts` that we end up using instead of our local `vscode.d.ts`. This change uses the `paths` `tsconig` option so that we use our local `vscode.d.ts` instead of the one from `node_modules` 2020-02-04 22:19:16 +00:00			`}`