[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

Commits

• 1e4744d Merge branch 'main' into ts7-release
• a5a219cmicrosoft/typescript-go#4558
• ecfe30d Update status localization
• 5de25b5 Hide executable name in TypeScript status
• d7ce74a Show bundled TypeScript version for packaged servers
• 29be66a Correct TS 7 release version to 7.0.2
• ed2bd1b Merge branch 'main' into ts7-release
• 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
• 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
• d4eaca5microsoft/typescript-go#4549
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[timsneath]

@dependabot rebase

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	plcc-web	fc6d5e3	Aug 25 2026, 05:10 AM

[timsneath]

Holding this one. The peer conflict CI reports is a symptom, not the cause.

TypeScript 7 is the native Go compiler, and its npm package no longer ships the JavaScript compiler API. The whole main export is now the version string:

// typescript@7.0.2 package.json
"exports": {
  ".": "./lib/version.cjs",          // `version` + `versionMajorMinor`, and nothing else
  "./unstable/sync":  "./dist/api/sync/api.js",
  "./unstable/async": "./dist/api/async/api.js",
  // ...the rest of the surface is namespaced `unstable/`
}

astro check is built on the API that went away. The chain is @astrojs/check → @astrojs/language-server → @volar/kit, and createChecker.js opens with const ts = require("typescript") before calling ts.sys, ts.readJsonConfigFile, createLanguageServiceHost(ts, ...). Under TS 7 every one of those is undefined. So @astrojs/check's typescript@"^5.0.0 || ^6.0.0" peer range is load-bearing, not conservative — do not force this through with --legacy-peer-deps. It installs, then dies at npm run check, because @astrojs/language-server already ships a guard for exactly this:

TypeScript's native compiler does not ship that API yet — require('typescript') only exposes version and versionMajorMinor — so continuing would crash later with an opaque Cannot read properties of undefined error.

Upstream tracking is withastro/roadmap#1321, quoting the TypeScript team: "TypeScript 7 does not yet expose a stable programmatic API, and so tools (such as Volar) which embed TypeScript into their own compilers and language services can only currently rely on TypeScript 6.0." No timeline.

Nothing in this repo blocks the move — no file touches the TS API, scripts/ and spike/ are .mjs, there are no enums, namespaces, decorators or .tsx, and every tsconfig.json option we use survives in 7. It's astro check alone, and that's the only type-check gate in ci.yml.

This PR is deliberately left open and red, as a tracker. The hold lifts when @astrojs/check widens its peer range:

npm view @astrojs/check peerDependencies

If that admits ^7, rerun CI here and merge if green. Written up in docs/development.md under "Dependency updates" (0f58249).

[timsneath]

Follow-up: tracing the blocker to its actual source, since @astrojs/check's peer range is only where it surfaces.

The chain is three deep:

1. TypeScript 7 ships no stable programmatic API. The native Go port's main export is the version string; everything else is namespaced unstable/. Stabilising the Language Service API is scheduled for 7.1 — microsoft/TypeScript#63703, the 7.1 iteration plan, which currently targets beta 9 Sept 2026, RC 20 Oct 2026, stable 10 Nov 2026.
2. Volar embeds that API, so it is pinned to TS 6 until (1) lands. Related design discussion on how embedded languages (.astro, .vue, .svelte) should be supported natively rather than by monkey-patching: microsoft/TypeScript#63772.
3. @astrojs/check is Volar, which is why its peer range stops at ^6 — withastro/roadmap#1321 is Astro's tracking discussion.

So the earliest realistic unblock is TypeScript 7.1, ~November 2026, plus whatever Volar and Astro need after that. Nothing to do here until then.

Worth noting for anyone tempted by a shortcut: there is no partial adoption worth having. A standalone tsgo --noEmit pass covers none of the 49 .astro files, and would fail outright on src/components/blocks/tina/registry.ts, which imports .astro components directly.

Now written up in docs/development.md under "Dependency updates" (c2216e0).

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	plcc-web	5925d24	Aug 28 2026, 12:58 AM

[timsneath]

Progress check, 9 Nov. Still blocked, but the picture has moved.

• TypeScript 7.1 slipped two weeks. The beta shipped 20 Oct. #63703 now plans the RC for 10 Nov and stable for 24 Nov (was 10 Nov). "Language Service API" is still an open item, and the 7.1 beta's API (typescript/sync, typescript/async, typescript/ast…) doesn't include one yet.
• @astrojs/check hasn't moved. 0.9.12 still peers on typescript ^5 || ^6, and @volar/kit 2.4.31 now says typescript: "<7" outright.
• New: a second way out that skips Volar. Astro merged @astrojs/ts-content-mapper (0.2.0 on npm). It lets tsc 7.1+ type-check .astro files directly, using the content-mapper hook TypeScript added in typescript-go#4712. This changes my earlier point about a standalone tsgo pass: on 7.1 with the mapper, it would cover our 49 .astro files and registry.ts. For now it needs a flag and has no end-to-end tests until 7.1 is stable, so it isn't ready to rely on yet.

So the hold lifts by whichever comes first: @astrojs/check admitting ^7, or replacing astro check in ci.yml with tsc + the content mapper once 7.1 is stable. The second option is a CI change, not just merging this bump. docs/development.md is updated to match (565d4dc).