Comments

Hacker News

Major ts pain point is scoping tsconfig settings for lib and types configurable for subsets of a project.

My project is a webapp, but I have node types in my ide tooling because of vite.config.ts, and playwright and unit tests. If I add a node api to a react component, tsc won't complain.

Current method to isolate dom lib from node lib requires project reference spaghetti, numerous tsconfig.json and tsbuildinfo output files, and avoiding emitting types with project references is cumbersome.

by mckee_plus_plus

No TypeScript compiler API yet, but I'm encouraged to hear that they're working on it.

by skybrian

Seeing these graphs of astounding performance gains with less memory requirements makes one wonder, Why am I using server-side TypeScript and not Go?

by Exoristos

I'm glad the JSDoc type syntax is still getting some focus. It's my favorite way to use typescript in my own projects. Some of the syntax changes will be annoying to update but most of them seem to be for the better.

by chroma_zone

After a few years of using Typescript, having to use type annotations and import basic language features like `abc` in Python feels like an absolute slog.

by miiiiiike

the real story here is an incredible team that managed to simultaneously keep two separate codebases alive for the most advanced type system known to mankind (yeahhh yeahh Hindley-Milner eat your heart out).

huge congrats to the team!

looking forward to the Rust rewrite ;)

by dimitropoulos

Remember when people would argue about how types weren't worth the effort?

I love TypeScript, if nothing else for how it's been able to popularize types.

by adamddev1

The speed up numbers based on their testing:

    Codebase    | TypeScript 6 | TypeScript 7 | Speedup
    ------------|--------------|--------------|--------
    vscode      | 125.7s       | 10.6s        | 11.9x
    sentry      | 139.8s       | 15.7s        | 8.9x
    bluesky     | 24.3s        | 2.8s         | 8.7x
    playwright  | 12.8s        | 1.47s        | 8.7x
    tldraw      | 11.2s        | 1.46s        | 7.7x
Congratulations to the team for pulling off this feat while doing a responsible migration (looking at you, Bun).

Quick question: How does this affect downstream tools like tsdown and esbuild, which need to build the TypeScript codebase? Can I use TS 7 and current tsdown together?

by m3h

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Major ts pain point is scoping tsconfig settings for lib and types configurable for subsets of a project.

    My project is a webapp, but I have node types in my ide tooling because of vite.config.ts, and playwright and unit tests. If I add a node api to a react component, tsc won't complain.

    Current method to isolate dom lib from node lib requires project reference spaghetti, numerous tsconfig.json and tsbuildinfo output files, and avoiding emitting types with project references is cumbersome.

  • No TypeScript compiler API yet, but I'm encouraged to hear that they're working on it.
  • Seeing these graphs of astounding performance gains with less memory requirements makes one wonder, Why am I using server-side TypeScript and not Go?
  • I'm glad the JSDoc type syntax is still getting some focus. It's my favorite way to use typescript in my own projects. Some of the syntax changes will be annoying to update but most of them seem to be for the better.
  • After a few years of using Typescript, having to use type annotations and import basic language features like `abc` in Python feels like an absolute slog.
  • the real story here is an incredible team that managed to simultaneously keep two separate codebases alive for the most advanced type system known to mankind (yeahhh yeahh Hindley-Milner eat your heart out).

    huge congrats to the team!

    looking forward to the Rust rewrite ;)

  • Remember when people would argue about how types weren't worth the effort?

    I love TypeScript, if nothing else for how it's been able to popularize types.

  • The speed up numbers based on their testing:

        Codebase    | TypeScript 6 | TypeScript 7 | Speedup
        ------------|--------------|--------------|--------
        vscode      | 125.7s       | 10.6s        | 11.9x
        sentry      | 139.8s       | 15.7s        | 8.9x
        bluesky     | 24.3s        | 2.8s         | 8.7x
        playwright  | 12.8s        | 1.47s        | 8.7x
        tldraw      | 11.2s        | 1.46s        | 7.7x
    
    Congratulations to the team for pulling off this feat while doing a responsible migration (looking at you, Bun).

    Quick question: How does this affect downstream tools like tsdown and esbuild, which need to build the TypeScript codebase? Can I use TS 7 and current tsdown together?

    by m3h