typescript-7

Configure new TypeScript 7 projects and port TypeScript 6 codebases to the Go-native compiler.

2|Updated May 16, 2026
One-click install
npx skills add https://github.com/avbel/ai-skills --skill typescript-7-avbel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-7
Source: https://github.com/avbel/ai-skills/tree/main/skills/typescript-7
Command: npx skills add https://github.com/avbel/ai-skills --skill typescript-7-avbel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? TypeScript 7 is a Go-native rewrite of the compiler with different configuration rules, removed options, and no stable programmatic API in 7.0, so teams risk broken builds, misconfigured tsconfig files, and incompatible tooling when adopting or migrating to it. ## Core Features & Use Cases - New Project Configuration: Provides a pinned, strict tsconfig baseline for Node.js 26 ESM projects using TypeScript 7, including module resolution and strictness flags. - TypeScript 6 to 7 Migration: Guides a staged port covering deprecation cleanup, removed configuration replacement, API-coupling inventory, and side-by-side compiler setups via the TypeScript 6 compatibility package. - Compiler Verification: Ships a bash script that validates the installed tsc executable and reports structured JSON results with specific error keys like wrong_major or compiler_not_executable. - Use Case: A team upgrading a large TypeScript 6 monorepo uses this Skill to inventory tools importing the typescript package, replace removed options like baseUrl and target es5, then verify the new compiler in CI before switching. ## Quick Start Ask the agent to configure this project for TypeScript 7 or to port the existing TypeScript 6 codebase and verify the installed compiler version.

Frequently Asked Questions about typescript-7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a project from TypeScript 6 to TypeScript 7?▼

Update to the latest TypeScript 6 patch, remove ignoreDeprecations, fix all 6.0 deprecations, and pass tsc --stableTypeOrdering first. Then inventory tools importing the typescript API, replace removed configuration, install TypeScript 7, and compare diagnostics, output, tests, and build performance.

What tsconfig options were removed in TypeScript 7?▼

TypeScript 7 turns TypeScript 6 deprecations into hard errors, including target es5, downlevelIteration, baseUrl, outFile, moduleResolution node/node10/classic, and module amd/umd/system/none. Replace them with nodenext or bundler resolution and raise the target to a supported runtime.

Can TypeScript 6 and TypeScript 7 run side-by-side in one project?▼

Yes, use the documented alias arrangement with @typescript/native mapped to typescript@^7 and typescript mapped to @typescript/typescript6. The compatibility package exposes only tsc6 while TypeScript 7 exposes tsc, so the binary names do not collide.

Does TypeScript 7 support the compiler API and tsserver plugins?▼

TypeScript 7.0's tsc and LSP are production-ready, but 7.0 does not expose a stable programmatic API. Tools importing the typescript package, custom transformers, and legacy tsserver plugins should remain on TypeScript 6 until they add explicit 7.x support.

Why does the TypeScript 7 compiler check fail with compiler_not_executable?▼

The compiler binary is missing or not executable, usually because dependencies were not installed or optional dependencies were omitted. TypeScript 7 uses platform-specific optional packages, so install with optional dependencies enabled and verify the compiler inside the target CI or container platform.