typescript-go icon indicating copy to clipboard operation
typescript-go copied to clipboard

Staging repo for development of native port of TypeScript

Results 434 typescript-go issues
Sort by recently updated
recently updated
newest added

Did some profiling of this overnight. - Eliminate the closures; this can be done through the same tricks used in the parser to avoid binding. This reduces some 10%+ allocations....

We try and import a type: ![Image](https://github.com/user-attachments/assets/2e99efc4-f30a-4d43-a1f8-1146317b0ea7) the file is a .d.ts ![Image](https://github.com/user-attachments/assets/aee4974e-4b40-4dc0-b1db-fa2936c85e8c) and it exports what we want to import: ![Image](https://github.com/user-attachments/assets/f16620c4-74f3-441e-8dec-f8ee507ab153) tsc does this fine but tsgo gives an...

Followup to https://github.com/microsoft/typescript-go/pull/971#discussion_r2114352757, but this makes creating globs a bit slower due to the FS accesses to see if things are symlinked.

The infamous `externalModuleIndicator` field requires access to info like the module setting of the closest package.json in order to work in some situations. This is normally "fine"; just make a...

```js const foo = [] for (let i = 0; i < 10; i++) { foo.push(i) } console.log(foo) ``` Nets: ``` Argument of type 'number' is not assignable to parameter...

Domain: JS

In `Herebyfile.mjs`, I wrote: ``` /** * @type {{ [K in keyof typeof rawOptions as {} extends Record ? never : K]: typeof rawOptions[K] }} */ const options = rawOptions;...

Hello TS team, in our TS project we have an issue regarding memory usage, certainly linked to a large monorepo types and configuration We managed to handle this by asking...

**with below code:** ``` export class X { static readonly ID = 'XXX'; } ``` generated d.ts file with below different: - **tsc** ``` export declare class X { static...

My project makes heavy use of [`react-hook-form`](https://github.com/react-hook-form/react-hook-form). A quick `git grep` tells me we have 310 forms. On two of them we are getting the "Type instantiation is excessively deep...

I'm not sure if this is a bug in the current or in the new compiler, but there is a scenario where some amount of logic involved determining the type...