2ee6b0b7b9
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
e8a8df7782
Bump all samples to Typescript 5.9
2025-08-06 23:43:14 -07:00
9fb82e1fb8
Bump package version for audit fixes
2025-03-03 09:59:28 -08:00
e3fce53668
Pick up latest TS version for all samples
2025-03-03 09:17:39 -08:00
774ecdb0ee
Bump ts-eslint versions
...
This fixes a warning about running on an unsupported TypeScript version. Also makes sure we do not lint any `.vscode-test` contents if they are present
2024-11-26 22:59:45 -08:00
e0fac10b63
Update all samples to TS 5.7
2024-11-26 19:16:22 -08:00
73e249b3c1
Migrate all samples to eslint 9
...
Switches all samples to use eslint 9 with flat configs. I've tried to migrate existing settings as much as possible. However our eslint configs were also inconsistent so I've tried to align these too
2024-10-26 17:44:03 -07:00
8465a39a90
Bump to TS 5.6.2
...
Also bumps `@types/node` to fix compat issues with new TS lib typings
2024-10-03 11:53:22 -07:00
7628cfc947
Bump eslint versions
...
Avoids a warning when running the linter with TS 5.5
2024-06-27 13:33:48 -07:00
6d620a3a1a
Bump to latest stable TS release for building samples
2024-06-26 17:02:58 -07:00
f4e09a3b7b
chore: update dependencies ( #996 )
...
- Update @vscode/test-electron due to some bugs
- Update @vscode/test-cli for modern goodness
- vscode-dts -> @vscode/dts off of the deprecated name
- @types/node to 18 to match VS Code itself
2024-04-02 01:29:31 +02:00
e28066f718
Build samples using TS 5.4
2024-03-14 16:47:53 -07:00
980bcbf2df
Pick up latest TS for samples
2023-12-05 10:51:43 -08:00
1e2b46108f
Update eslint versions
...
Supports the new TS version
2023-09-13 14:45:34 -07:00
c19df22319
Update all samples to use TS 5.2.2
2023-09-11 13:29:22 -07:00
3ca4acdff2
Bump extensions to TS 5.1
...
Picks up TS 5.1.3 for building extensions
Also bumps `@types/node` to resolve typings conflicts with new TS version
2023-06-05 14:34:14 -07:00
a4a557c49d
Bump samples to use TS 5.0
2023-03-20 14:42:14 -07:00
5d3686b7dc
Bump old vscode versions
...
This bumps the `@types/vscode` and `engines: vscode` on packages that were using very old versions. These old versions used a `vscode.d.ts` that didn't include proper link support. We've also made a number of fixes and improvements to `vscode.d.ts` that are useful to extension authors
2023-01-30 21:11:11 -08:00
4a232d8b4e
Pick up TS 4.9 for building samples
2023-01-30 10:35:24 -08:00
42e83bf2f3
Bump eslint versions and update lint scripts
...
Pick up latest eslint to avoid a nasty warning about using an unsupported version of TS
Also updates the eslint script to be more scoped on which files it checks
2022-11-04 13:52:32 -07:00
b56a580d1e
Pick up latest TS for building samples
2022-09-27 15:01:41 -07:00
5b10219434
Bump eslint TS versions
...
This fixes the warnings about using an unsupported version of typescript
2022-06-28 15:25:09 -07:00
44683d707f
Use node typings from current VS Code
2022-05-24 15:12:22 -07:00
f7f5bee0e5
Update to TS 4.7
2022-05-24 15:04:19 -07:00
6bd0a97459
Bump eslint package versions
2022-04-13 15:49:42 -07:00
828768a62c
Use latest TS version for all packages
...
This also updates our package-locks to v2
2022-04-13 15:12:23 -07:00
2bc23042f1
Update samples to build with TS 4.5.5
2022-02-09 11:38:40 -08:00
355d5851a8
Build extensions using TS 4.4
2021-10-04 12:24:14 -07:00
95618adb09
Bump minor TS version
2021-07-13 18:48:28 -07:00
a92db32ca1
Adding repo and license fields to samples that were missing them
2021-06-11 17:10:40 -07:00
1f9cfe91f1
Bump samples to TS 4.3
2021-06-11 17:00:34 -07:00
5489dd3629
Sorting installs
2021-03-02 16:02:01 -08:00
54053dd917
Pick up new eslint versions
2021-03-02 15:59:42 -08:00
32e50e81c0
Use TypeScript 4.2 for building all samples
2021-03-02 15:48:43 -08:00
23e5167c2f
Update samples to compile with TS 4.0.2
2020-09-10 15:20:30 -07:00
aaa7e1baf9
Remove proposed api from tasks package.json
2020-06-09 10:10:28 +02:00
ee16257d90
Update tasks custom sample to not use proposed api
...
Related to https://github.com/microsoft/vscode-extension-samples/issues/306
2020-06-09 10:07:50 +02:00
2c377b7828
Update extensions to build with typescript 3.9.4
...
Also fixing some compile errors in configuration-sample
2020-05-29 14:11:10 -07:00
7b9a0a8c4c
Use eslint instead of tslint
...
Fixes #266
2020-05-29 14:01:37 -07:00
e8da8b531a
Update tslint version to 5.19
...
This fixeds a few vulnerabilities listed when running `npm i`
2020-04-14 18:05:51 -07:00
209a84c1af
Bump all samples to use TS 3.8.3
...
Also required bumping `@types/node` to 12.12.x
2020-04-14 18:01:21 -07:00
b6158195a3
Updating npm run install to pass
2020-01-08 22:08:36 -08:00
0d75c54755
Update task provider sample
...
CustomExecution2 -> CustomExecution
2019-10-21 11:49:13 +02:00
89b73121aa
Add a sample for CustomExecution tasks
2019-08-06 14:03:07 +02:00
4c2ba979fc
Us TS 3.5.1 for all samples
2019-05-31 11:51:11 -07:00
f4f21dcb03
Bump tslint versions
...
Fixes some npm audit issues
2019-05-09 17:04:08 -07:00
139fa5b39a
Use latest TS version across examples
2019-05-09 16:59:56 -07:00
0b26276bb6
Use vscode/@types for most extension samples
...
Fixes #180
Changes from using `vscode` to `@types/vscode` for the majority of extension samples. The `@types/vscode` package is much smaller and does not pull in any dependencies.
Other changes:
- Remove so empty test files
- Bump engine versions to match @types/vscode versions
- Use `npm run compile` for most `vscode:prepublish` scripts
2019-05-09 14:52:38 -07:00
655ea9dc0a
Fix path to task-provider-sample's main
...
It's built to out/extension.js, so launching the extension currently produces an error. I guess that was caused by this change:
704f351abd (diff-71ee4bf336efb1f169e66d21bbc6d508)
2019-02-06 14:22:26 +01:00
704f351abd
Update task provider sample
2018-10-26 12:25:53 +02:00
