Hey @yoavbls,

I recognize you are from Israel and have been silent since the Hamas attack on the Israeli people.

I want to express my solidarity, and I hope you & your family are doing okay in those challenging times.
Your work is truly incredible, you have built a great piece of software that is making the lives of thousands of developers a lot easier.

I hope you will find peace in Israel & Palestina somehow in the future.

Best,
Felix

We need your votes on things we can't do ourselves because it depends on others
(e.g. VSCode and TypeScript teams on Microsoft, JetBrains, etc)

Please help us help everybody by voting in the links below 💙

1. Make types copyable

Solves #29

I made an issue + pull request for VSCode.
VSCode team may reject it because they already rejected requests for new style props before and promised to solve this in a more robust method, which didn't happen in the last 3 years.
So please:

⬆️ Upvote or comment here

2. Allow diagnostics messages to have markdown

Solves #15, #19, #3 and make us closer to solve: #11, #21, #26, #25

If VSCode allows it we could be able to move the formatting to a language server plugin which will allow us to:

1. Control the order of the original error and the pretty one
2. Hide the original error without losing it in the problems pane in VSCode or for other extensions like Error Lens
3. Support more platforms more easily like Neovim, Visual Studio and maybe even JetBrains IDEs

⬆️ Upvote or comment here

3. JetBrains support

solves #11.

We saw a huge demand for support WebStorm and other JetBrains IDEs.
This ticket on YouTrack probably got JetBrains attention:

⬆️ Upvote or comment here

If you're a person from the relevant JetBrains team, please reach me out 💙

THANK YOU ALL! 💁🏼‍♀️

Saying I have this error :

When I hover over the error I see this :

it showes errors in two formats: raw& beautify

Expected : to see only the beautified error

Describe the bug
I just installed this extension. However, no dialogue box pops up when I hover over a red line error.

Expected behavior
I expected a dialogue box to appear with information on the error when I hovered over it.

Original error
If this bug is related to an error that is not formatting well, please
attach the original error in a code block:

Type: Bug

whenever I press save on ts file; it gives semantics error in notification and when done bisect debug within vscode; this extension is the cause of the issue. I am not sure about it but having issues.

Extension version: 0.5.3
VS Code version: Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:10.514Z)
OS version: Windows_NT x64 10.0.22000
Modes:

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vsclangdf:30486550
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30933248
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019a:30933241

Really loving the format of these errors! It's a lot easier to read.

The only thing I noticed is that the unformatted errors are still showing up. Was this intended or is there a way to remove them?

Update / TLDR

This is currently intentional but there are plans to improve the experience. This could potentially be improved by:

• Removing the original error
• Changing the order of the errors so that the pretty version is on top

The issue is that the improvements rely on changes to VS Code. Go upvote this issue if you want these changes!

@yoavbls wrote:

This is the issue that will eventually allow us to modify the order of the errors + mute the original error:
microsoft/vscode#54272

• Issue Type: Performance
• Extension Name: pretty-ts-errors
• Extension Version: 0.5.1
• OS Version: Linux x64 6.4.6-76060406-generic
• VS Code version: 1.81.1

⚠️ Make sure to attach this file from your home-directory:
⚠️file:///tmp/yoavbls.pretty-ts-errors-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

Describe the bug
I noticed that I did not get any prettified errors when working from a .vue file.

I setup a basic snippet like:

<script setup lang="ts">
import { RouterView } from 'vue-router';

const x = [1, 2, 3, '4'];

function y(param: number[]) {

}

y(x); 

</script>
<template>
    <RouterView />
</template>

And per screenshot the highlighter result:

Expected behavior
I expected to see a prettified error message as vue support is implemented.

Cause
I cloned the repo and ran it with the debugger and found that this issue is caused by the following:

On this line the value of uri.path is: '/c:/Users/kevin/Documents/Projects/phavuer-playground/src/App.vue'

When in the hoverProvider.ts:

The value of document.uri.path is '/C:/Users/kevin/Documents/Projects/phavuer-playground/src/App.vue'.

Notice the casing difference of the C drive:

- '/c:/Users/kevin/Documents/Projects/phavuer-playground/src/App.vue'
+ '/C:/Users/kevin/Documents/Projects/phavuer-playground/src/App.vue'

This causes the hoverProvider to think there are no stored items to show, and thus show no results.

Fix
VS Code seems to use this implementation for the Uri class.

Maybe use fsPath instead as it states:

/**
* Returns a string representing the corresponding file system path of this URI.
* Will handle UNC paths, normalizes windows drive letters to lower-case, and uses the
* platform specific path separator.
*
* * Will *not* validate the path for invalid characters and semantics.
* * Will *not* look at the scheme of this URI.
* * The result shall *not* be used for display purposes but for accessing a file on disk.
*
*
* The *difference* to `URI#path` is the use of the platform specific separator and the handling
* of UNC paths. See the below sample of a file-uri with an authority (UNC path).
*/

Now

CONTRIBUTING.md contains only the following one line, which has little content and does not function well as a guideline.

Contribute good stuff

Moreover, a link to this file is shown as a guideline on the following page.

• Top of issues
• Top of Pull Requests
• Screen for filling out an issue

This is a capture of the current screen

Top of issues	Top of Pull Requests	Screen for filling out an issue

Expected

Would you change the content of CONTRIBUTING.md to the following?

* Any other contribution is welcome. Feel free to open any issue / PR you think.
* Bug reports should be filed in accordance with the bug report template.

can we also get this plugin work for the fixed box ?
thank

Describe the bug
When the exteention is enabled, whenever I open vscode, the Typescript server starts to spin up but it never finishing spinning up. this behaviour makes the code editor unusable. I can't see linting or intellesense, the files don't save, and nothing works.

After disabling the extension, everything returned to normal.

This only started to happen Yesterday, Augest 23rd. before that, the extension was working normally.

Expected behavior
Everything should work normally.

Hi, This plugin is awesome and helpful.
And I am wondering if you have plans to support JetBrains WebStorm.

Best regards.

Describe the bug
If a setting as such is used:

{
  "typescript.validate.enable": false, // <- this is the setting
  "eslint.validate": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact"
  ]
}

no errors pretty-ts-errors are displayed. only the ESLint ones as shown in the following image:

If we change this to true we now get all 3 validations: which is not desirable:

Expected behavior
Being able to use the following setting and still be able to see the pretty errors and probably the eslint errors, but not the ts ones:

{
  "typescript.validate.enable": false
}

Great plugin!
Any plans to bring this joy to us developers who use Visual Studio 2022?

Thanks!

Describe the bug
ts(4113) and ts(4117) are formatted incorrectly if the base class is generic and there are quotes in the base class part of the error.
For example:
ts(4113)

class A<T extends string> {}

class B<T extends { nested: string }> extends A<T["nested"]> {
	override test: any;
}

ts(4117)

class A<T extends string> {
	public testA: any;
}

class B<T extends { nested: string }> extends A<T["nested"]> {
	override test: any;
}

Expected behavior
It should probably be formatted as:

This member cannot have an override modifier because it is not declared in the base class A<T["nested"]>. ts(4113)
and
This member cannot have an override modifier because it is not declared in the base class A<T["nested"]>. Did you mean testA?ts(4117)

Original error
If this bug is related to an error that is not formatting well, please
attach the original error in a code block:

This member cannot have an 'override' modifier because it is not declared in the base class 'A<T["nested"]>'.ts(4113)
This member cannot have an 'override' modifier because it is not declared in the base class 'A<T["nested"]>'. Did you mean 'testA'?ts(4117)

Screenshots

Original error

Argument of type '{ filters: Filters; } & T' is not assignable to parameter of type 'T & F'.
  Type '{ filters: Filters; } & T' is not assignable to type 'F'.
    '{ filters: Filters; } & T' is assignable to the constraint of type 'F', but 'F' could be instantiated with a different subtype of constraint '{ filters: Filters; }'.ts(2345)

Screenshots

Describe the bug
The problem in formatting type 'F', but 'F' could and constraint '{ filters: Filters; }'.

I checked out the repo locally and used npm ci to install the packages from the package-lock.json.
I ran npm run test in the command line, it fails with the following output:

$ npm run test

> [email protected] pretest
> npm run compile-tests && npm run compile && npm run lint


> [email protected] compile-tests
> tsc -p . --outDir out


> [email protected] compile
> node scripts/build


> [email protected] lint
> eslint src --ext ts & tsc --noEmit


> [email protected] test
> node ./out/test/runTest.js

Downloading VS Code 1.87.2 from https://update.code.visualstudio.com/1.87.2/win32-x64-archive/stable
gzip: stdin has more than one entry--rest ignored
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at doWrite (node:internal/streams/writable:411:12)
    at clearBuffer (node:internal/streams/writable:572:7)
    at onwrite (node:internal/streams/writable:464:7)
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:106:10)
Emitted 'error' event on Socket instance at:
    at Socket.onerror (node:internal/streams/readable:785:14)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4047,
  code: 'EPIPE',
  syscall: 'write'
}

I tried this both on node 20 and 18. Looking at https://github.com/microsoft/vscode-test/issues they suggest updating to the latest version.

I checked the package-lock.json and noticed it is locked at 2.3.3. When I updated the package to 2.3.9 the test suite runs and succeeds as expected.

I will add an PR with the fix.

Syntax highlighting should be fixed in other languages(Korean, in this case).
If you're unfamiliar with other languages that reproduce these kinds of issues, I'll try to contribute PR with this issue.

Type: Bug

type something

Extension version: 0.5.3
VS Code version: Code 1.82.0 (Universal) (8b617bd08fd9e3fc94d14adb8d358b56e3f72314, 2023-09-06T22:09:41.364Z)
OS version: Darwin arm64 22.6.0
Modes:

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
0bi6i642:30951795
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019bcf:30953938
3ef8e399:30949928

I don't see any new formatting after I enabled (and restarted VS Code, just to be safe) extention:

Could there be some kind of conflict with other extensions?

I only installed this awesome extension recently, but with recent changes to the vscode vue language tool extension, it seems that this extension is not formatting the error messages within .vue files (It works fine on .ts files)

Is anyone else running into this problem, or is this a setup problem on my end for some reason? (Or perhaps an issue with the Vue language tools since there's many issues open currently)

Working just fine on .ts files.

On a .vue file

Vue Language Tool / Vue - Official extension version: v2.0.10
Vscode version: 1.88.0
Running @Builtin js and ts language features *No takeover mode)

Hi, thank you for the great extension. I installed this extension and but for some reason, I still get the same ts error style

Describe the bug
Hi, since today this extension has been causing the save file action to hang indefinitely.
I deactivated all my VSCode extensions and this one seems to cause the issue. I don't have any more insight but I'll be happy to send more if someone provides guidance.

I use the v0.5.2 and also tried the v0.5.1 which causes the same issue.

Here's my VSCode info:

Version: 1.84.2
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:52:57.054Z (1 wk ago)
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 21.5.0

Expected behavior
Saving a file should be instant.

Screenshots

Describe the bug
ts(1378) is not handling the use of multiple single quotes correctly, putting all of the code instances into a single block, plus text in between.

Expected behavior

I'd expect the message to look something like:

Top level await expressions are only allowed when the module option is set to es2022, esnext, [...] or nodenext, and the target option is set to es2017 or higher.

Original error

Top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher.ts(1378)

Screenshots

I don't know what to say here, but yeah whatever

Type: Bug

I absolutely love this extension and can't live without it.
But I noticed that I very consistently have lags in typing when using it (the UI will freeze for split seconds while typing). I don't know what the reproduction steps are, but I used the Extension Bisect tool to identify that this only happens when the extension is active (and very consistently) and never when the extension is deactivated.

Extension version: 0.2.8
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:41:48.638Z)
OS version: Darwin arm64 22.3.0
Modes:
Sandboxed: Yes

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1:30587005
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
vsctsb:30705553
functionswalk:30687959
pythonms35:30701012
pythonfmttextcf:30716743

Describe the bug
Cannot install to a vscode remote server via ssh, press install and it always installing.

Expected behavior
Extension can be installed to remote server.

Original error

Screenshots

Method's 'this' got read incorrectly. Probably, incorrect use of ' or ".

We need a change in VSCode to allow that. I opened a PR and Issue there:
microsoft/vscode#180496
any other ideas will be welcomed

Hello!

I feel like it would be nice to open discussions, your work on making the errors works will definitely interest other devs and VSCode itself

Type: Bug

Visual Studio Code suddently started running extremely slow. I ran Extension Bisect which found this extenson to be the culprit. After disabling it, vscode is back to normal.

I re-enabled it just to be sure and vscode was extremely slow again. I also noticed backspace no longer works when this extension is running.

Extension version: 0.5.3
VS Code version: Code 1.88.0 (5c3e652f63e798a5ac2f31ffd0d863669328dc4c, 2024-04-03T13:28:18.899Z)
OS version: Darwin x64 22.6.0
Modes:

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
jchc7451:30973076
gee8j676:31009558
dsvsc021:30996838
g1icg217:30999571

Describe the bug
The error formatting is odd and is displaying what appears to be an icon that isn't properly interpolated.

This is the line that caused the error:

return (control.value > max) ? { maxDate: true } | null;

The error is being caused by accidentally typing | instead of :, but the formatting of the error is strange.

I haven't seen any other instances like this and I've been using this extension for the past week.

Expected behavior
To show the styled error.

Original error
The left-hand side of an arithmetic operation must be of type 'any', 'number', 'bigint' or an enum type.

Screenshots
If applicable, add screenshots to help explain your problem.

Type: Bug

I am unable to do any development in my VS code with the any extensions I have installed.

Extension version: 0.5.1
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.19045
Modes:

vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
3biah626:30602489
89544117:30613380
showlangstatbar:30737416
0bi6i642:30835152
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
asynctok:30821568
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30829745

Describe the bug
Hovering over the error in:

const x: "' 'Oh no" = null;

The formatting is broken

Type null is not assignable to type "'Oh no"'.

Expected behavior

Type null is not assignable to type "' 'Oh no".

Original error
Type 'null' is not assignable to type '"' 'Oh no"'.ts(2322)

Screenshots

I had an issue while using deno and deno linter (emits deno-ts errors)

No problem with regular ts errors in node. Maybe some options should be swithced on?

Spec:
deno 1.32.4 (release, x86_64-pc-windows-msvc)
v8 11.2.214.9
typescript 5.0.3
vscode 1.77.3
Win 11

Type: Bug

Source control is throwing a time out

Extension version: 0.5.3
VS Code version: Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:10.514Z)
OS version: Windows_NT x64 10.0.22621
Modes:

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
0bi6i642:30933247
f8hc8238:30694864
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019acf:30933242

• Issue Type: Performance
• Extension Name: pretty-ts-errors
• Extension Version: 0.4.0
• OS Version: Windows_NT x64 10.0.19044
• VS Code version: 1.78.0

⚠️ Make sure to attach this file from your home-directory:
⚠️file:///c%3A/Users/LENOVO/AppData/Local/Temp/yoavbls.pretty-ts-errors-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

Thanks for making such a nice library, I know my question is not specifically related to this repo, but I'm guessing you guys might know the answer.
I would like to remove the duplicate .ts error on hover, Do you have any idea around it?

As you know the fist line of the error is almost redundant.

Describe the bug
When writing code in React, I often need to transfer props to the parent component. However, I sometimes forget which props need to be omitted when passing them to the parent component.

Expected behavior
I expect to have a clear and convenient way of determining which props should be omitted when passing them to the parent component.

LanguagePicker.tsx

type languagePickerProps = {
  pickerProps?: DropDownPickerProps<Object>;

  // Omit<
  //   DropDownPickerProps<Object>,
  //   "multiple" | "setValue" | "value" | "items" | "open" | "setOpen"
  // >;
};

export const LanguagePicker = (props: languagePickerProps) => {
  // Component logic here
};


Footer.tsx

<LanguagePicker
  pickerProps={{
    style: {
      backgroundColor: "red",
    },
  }}
/>

Screenshots

Props needs to be shown in code format I think.

Please provide more context or additional information if necessary to help identify and resolve the issue.

Hi, This plugin is wonderful. Do you have any plans to support Neovim too?

Type: Bug

Problem: "yoavbls.pretty-ts-errors

Extension version: 0.5.2
VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:29:51.160Z)
OS version: Darwin arm64 22.5.0
Modes:

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30880073
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
vscrpc:30673769
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
synctok:30869157
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30871694
pythonregdiag2:30871582
pyreplss2:30879913
pythonmypyd1:30879173
pythoncet0:30874138
pythontbext0:30879054
dsvsc016cf:30880770
dsvsc018cf:30880895

I'm just linking the discussion there:
zed-industries/zed#7844

It looks like TypeScript LSP plugin will be the best solution to support more IDEs (Zed, NeoVim, Vim, CLI)

tsc --noEmit | pretty-ts-errors

As shown in the picture, after installation, the error highlighting is gone.

As the title, what is the minimum version it supports?
I can't install it in an old version of vscode 1.70.2

ScreenShot

Case

const a = { 'a-a': '11' }

const b:a = '11'

Describe the bug
When writing code in React, I often need to transfer props to the parent component. However, I sometimes forget which props need to be omitted when passing them to the parent component.

Expected behavior
I expect to have a clear and convenient way of determining which props should be omitted when passing them to the parent component.

LanguagePicker.tsx

type languagePickerProps = {
  pickerProps?: DropDownPickerProps<Object>;

  // Omit<
  //   DropDownPickerProps<Object>,
  //   "multiple" | "setValue" | "value" | "items" | "open" | "setOpen"
  // >;
};

export const LanguagePicker = (props: languagePickerProps) => {


Footer.tsx

  <LanguagePicker
          pickerProps={{
            style: {
              backgroundColor: "red",
            },
          }}
        />

Screenshots

It needs to be written in code format:

Please provide more context or additional information if necessary to help identify and resolve the issue.

The extension is not supported in this version of vscode