Zed shipped TypeScript-focused improvements this week. The changes target areas where Zed had been lagging: complex completions, type-check performance, and integration with TypeScript-specific tooling.
For TypeScript-heavy developers who’d been on Cursor or VS Code specifically for the TypeScript experience, this closes meaningful gaps.
What’s improved
Faster type-checking on save. The previous version’s type-check was sometimes slow; the new version uses TypeScript’s incremental mode more aggressively. Type errors appear within a second of save.
Better complex completions. Generic types, conditional types, mapped types — these had weaker completions than VS Code’s. The new version handles them comparably.
Auto-import improvements. Better detection of which import path to use. The previous version sometimes used absolute paths when relative was preferred (or vice versa). Now configurable per project.
TypeScript LSP speed. The TypeScript language server runs faster on large codebases. Indexing time is meaningfully shorter.
Better error reporting. TypeScript errors are formatted more clearly. Long error messages (with type expansion) collapse to readable summaries.
What’s still rough
Some advanced patterns. Discriminated unions with deep nesting, recursive types — completions can lag.
Some monorepo configurations. project references work but some setups have issues.
TypeScript plugin support. VS Code has rich plugin ecosystems for things like Tailwind autocomplete via TypeScript. Zed’s equivalent is less mature.
These are bounded; the bulk of TypeScript work is improved.
A practical comparison
For a typical React+TypeScript project:
VS Code: Good. Long history of TypeScript support. Reliable. Cursor: Same as VS Code (it’s a fork). Plus AI integration. JetBrains WebStorm: Excellent. Best-in-class for some operations. Zed: Now competitive with VS Code/Cursor. Faster overall.
For users picking on TypeScript experience alone, Zed is now in the same tier. Other factors (AI features, ecosystem, team adoption) become the deciders.
What this means for tool choice
Zed’s TypeScript improvements remove one reason to stay on Cursor for TypeScript work. Combined with Zed’s other strengths (speed, vim mode, native AI), the case for Zed adoption strengthens for some users.
This isn’t a “switch to Zed” recommendation. The choice depends on:
- AI feature requirements (Cursor is more mature)
- Team standardization (VS Code is everywhere)
- Specific extensions you depend on
- Personal preferences
But “Zed has weaker TypeScript” is no longer a reason to stay away. For TypeScript developers evaluating editors, Zed is a credible option.
Why this matters
The competitive dynamics in editor space:
- Cursor leads on AI integration
- VS Code/Copilot leads on extension ecosystem
- Zed leads on speed, native experience
- JetBrains leads on IDE features
Each has gaps in its non-strength areas. Zed’s TypeScript improvement closes one of its gaps.
The next year of editor competition will be about closing gaps. Zed adding more language polish, Cursor adding more native features, VS Code adding more AI capabilities. Users benefit from the pace.
A small but meaningful release
This is the kind of release that doesn’t make headlines but matters for daily users. TypeScript developers will notice the improvements without being told.
The cumulative effect of these incremental improvements is what shifts editor choice over time. No single release is decisive. Many small releases compound.
For Zed: this is consistent with their pattern of iterative polish. The product gets meaningfully better release-over-release.
Worth updating?
For Zed TypeScript users: yes. The improvements are real and immediately felt.
For users on other editors: doesn’t change much. Continue with your current setup unless you were considering switching anyway.
For evaluators: Zed’s TypeScript story is now strong. One less concern when evaluating Zed for serious work.
Closing
A useful release for a meaningful user base. The category of “TypeScript developers wanting a fast editor” now has Zed as a credible option.
The market keeps maturing. Editors keep improving. Users keep benefiting. The pace is good for everyone except the engineers who have to maintain the tools.
