Valentin Gurkov
Valentin Gurkov
For me, restarts of VSCode have always fixed the debugger not starting. I'm not sure this problem is related to the extension.
If you open the VSCode settings and search for `font`, you will see the option of configuring the font family for the editor, code lens, etc. Then all you need...
It seems that things like ```ts @Route(`v1/products/${ProductTypeKeysEnum.TRAINING}`) ``` also can't get evaluated.
Same here, does not run on iOS 15. Seems to work on 16.
For us, it turned out to be related to the content security policy. Safari 15 was blocking the request due to the `script-src` not allowing this domain. Because of this...
I'm experiencing the same unfortunately, does anybody know of a workaround that does not involve suppressing the warnings? Because on a large monorepo with microservices, we've got something like: `Only...
> This seems like a character limit on the check run summary. > > > does anybody know of a workaround that does not involve suppressing the warnings > >...
> using Node v20.6.1 it works Yes, `toSorted` is not available in Node 18. Not related to `ts-jest`. See [Array.prototype.toSorted() - Browser compatibility](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/toSorted#browser_compatibility).
I just added Turborepo to my monorepo and encountered this when installing the VSCode extension. I am using a local installation of turbo.
The peer dependencies on the React package have been updated to list React 19, but I have not done any tests with it.