typescript-go
typescript-go copied to clipboard
Staging repo for development of native port of TypeScript
Trying to get the NOTICE generation to work again.
The following minimal program passes `tsc` but fails `tsgo`: ```ts function doSomething(program: WebGLProgram) { void program; } const gl = document.createElement('canvas').getContext('webgl2'); if (!gl) { throw new Error('WebGL2 context not available');...
I don't fully understand the impact of this (perhaps none since the comments indicate this is just an optimization) but this code https://github.com/microsoft/typescript-go/blob/e7a30f5106f7af66974b59bba2d9510c11b7bfb6/internal/vfs/utilities.go#L216-L224 will produce different results depending on if...
Below line will be lost in compiled JS file: https://github.com/microsoft/vscode/blob/5a4e405ee0e6ff91e17ac6bf3f3b7efd34353ca1/src/vs/base/common/uri.ts#L6 ```ts import { CharCode } from './charCode.js'; import { MarshalledId } from './marshallingIds.js'; import * as paths from './path.js'; import...
I'm getting an issue where tsgo doesn't recognize an import that is working with normal tsc. relevant versions: ```json { "dependencies": { "@typescript/native-preview": "^7.0.0-dev.20250529.1", "bwip-js": "^4.5.1", "typescript": "^5.8.3" } }...
I think this is right; within a Project, cache the FS accesses and clear them out on graph update for safety. Then, things get faster in load time in module...
Program to take ParsedCommandLine as config instead of separate options, root names, diagnostics etc
The server also has to ask for these if enabled. Arguably, these should just get moved into semantic diagnostics, but... (Maybe this is too buggy/slow to expose in the editor...