TypeScript 7 can type-check ordinary TypeScript projects with a much faster native compiler, but framework files are more complicated. Astro components, Vue single-file components, Svelte files, MDX, and Angular templates embed TypeScript inside another language. Their tools often import the TypeScript compiler API to build virtual files and map diagnostics back to the original template.

TypeScript 7.0 does not expose the stable programmatic API those integrations expect. The TypeScript team therefore warns that many embedded-language workflows cannot fully adopt TypeScript 7 yet.

Quick answer

Use TypeScript 6 for framework-aware editor support and framework checks until the relevant integration announces TypeScript 7 support. You can evaluate TypeScript 7 on extracted .ts and .tsx code or a separate command-line check, but do not replace the framework’s official checker blindly.

{
  "scripts": {
    "check:framework": "astro check",
    "check:native": "tsc --noEmit",
    "build": "astro build"
  }
}

All three commands answer different questions. A successful native tsc does not validate template expressions or component-specific semantics.

Why embedded files need more than tsc

A .vue, .svelte, or .astro file is not handed directly to TypeScript exactly as written. Framework tooling creates TypeScript-shaped virtual code, asks TypeScript for diagnostics and language features, then maps positions back to the source file.

That integration can depend on compiler internals, language-service plugins, or APIs that are absent in TypeScript 7.0. The JavaScript and TypeScript inside a component may be valid while auto-imports, rename, template diagnostics, or source maps fail.

Angular projects have an additional template compiler. The TypeScript team suggests that Angular can use TypeScript 7 for fast project-wide command-line error detection in some cases while keeping TypeScript 6 for editor and template support.

Test the actual developer workflow

Do not limit the experiment to npm run build. Open representative component files and check:

  • diagnostics inside frontmatter or script blocks;
  • template expressions and component props;
  • rename across script and template boundaries;
  • go-to-definition into imported components;
  • auto-import suggestions;
  • generated declaration files;
  • source-map locations after a runtime error.

Use a small branch and record the framework extension, language server, TypeScript package, editor, and Node.js versions. Compatibility can depend on all of them.

npx astro check
npx tsc --noEmit --pretty false
npm run build
npm test

For Vue use the supported vue-tsc workflow; for Svelte use svelte-check; for Angular use the Angular compiler. Those checks remain authoritative for framework semantics.

Keep editor and CI versions understandable

VS Code can run a different TypeScript language server from the one installed in the project. With TypeScript 7, that difference becomes more important. A developer may see native editor diagnostics while CI uses an integration built on TypeScript 6.

Add a short repository note describing:

  • which command validates plain TypeScript;
  • which command validates framework files;
  • which editor server is expected;
  • which failure should block merging;
  • how to return to TypeScript 6.

Avoid committing workspace settings that force TypeScript 7 for every contributor until the framework integration is proven.

A safe hybrid rollout

Start with a package that contains plain TypeScript utilities and no embedded files. Measure native TypeScript there. Next, run TypeScript 7 on the framework project’s generated or ordinary .ts files without replacing the framework checker.

Keep TypeScript 6 available through @typescript/typescript6 if a tool imports the old API. When the framework announces support, remove the compatibility layer in a separate change and repeat editor, build, and runtime smoke tests.

Do not interpret “the site builds” as complete success. The biggest regression may be a broken rename or missing template diagnostic that appears days later during normal development.

Keep one framework-specific file in the smoke test: an Astro component frontmatter block, a Vue or Svelte component, an MDX expression, or an Angular template binding. Plain .ts coverage cannot prove that embedded language extraction, mapping, and diagnostics still work.

Test both diagnostics and navigation in that fixture.

Primary references

TypeScript 7 is ready to test, but framework readiness belongs to the full toolchain. Keep the official framework checker in charge until its maintainers support the new API and language server end to end.