vscode-extension-samples/lsp-sample/server/tsconfig.json

{
	"compilerOptions": {
		"target": "ES2024",
		"lib": [
			"ES2024"
		],
		"module": "commonjs",
		"moduleResolution": "node",
		"sourceMap": true,
		"strict": true,
		"outDir": "out",
		"rootDir": "src"
	},
	"include": [
		"src"
	],
	"exclude": [
		"node_modules",
		".vscode-test"
	]
}
Allign standard lsp example with new lsp structure 2017-09-04 17:43:23 +02:00			`{`
			`"compilerOptions": {`
Update all of our samples to target VSCode 1.100 or newer This makes sure that if folks get a relatively recent `vscode.d.ts`. It also lets us safely bump up the target to es2024 so you can use all the latest lib additions 2025-08-07 07:57:14 -07:00			`"target": "ES2024",`
			`"lib": [`
			`"ES2024"`
			`],`
Allign standard lsp example with new lsp structure 2017-09-04 17:43:23 +02:00			`"module": "commonjs",`
			`"moduleResolution": "node",`
			`"sourceMap": true,`
Enable strict mode for many samples 2019-05-10 14:34:54 -07:00			`"strict": true,`
Rename lsp-multi-root-sample to lsp-sample and delete old one 2018-06-04 12:10:27 +02:00			`"outDir": "out",`
Don't set explicit `lib` in tsconfigs The one we get from the `target` is correct in almost all cases for VS Code 2019-05-30 18:24:08 -07:00			`"rootDir": "src"`
Allign standard lsp example with new lsp structure 2017-09-04 17:43:23 +02:00			`},`
Update all of our samples to target VSCode 1.100 or newer This makes sure that if folks get a relatively recent `vscode.d.ts`. It also lets us safely bump up the target to es2024 so you can use all the latest lib additions 2025-08-07 07:57:14 -07:00			`"include": [`
			`"src"`
			`],`
			`"exclude": [`
			`"node_modules",`
			`".vscode-test"`
			`]`
			`}`