Migrate Node.js and Next.js projects to the native TypeScript 7 compiler.
npx skills add https://github.com/r-senchuk/agentskills --skill typescript-7-r-senchuk
Please help me install this Agent Skill. Skill: typescript-7 Source: https://github.com/r-senchuk/agentskills/tree/main/.agents/skills/typescript-7 Command: npx skills add https://github.com/r-senchuk/agentskills --skill typescript-7-r-senchuk
@typescript/typescript6 compatibility package with npm aliases so TypeScript 7 runs as tsc while API-dependent tools stay on TypeScript 6. - Deprecation Cleanup and Validation: Resolves TypeScript 6 deprecations without ignoreDeprecations, then validates tsc --noEmit, build, lint, and editor language-server behavior. - Use Case: A Next.js 16 project fails pnpm build after bumping typescript to 7.x; this Skill diagnoses the failing tool, applies the alias setup, and verifies the full toolchain. ## Quick Start Upgrade this project to TypeScript 7, keep any compiler-API tooling on TypeScript 6, and validate the build, lint, and type-check commands.High-intent search queries and answers about installing and using this skill.
First resolve all TypeScript 6 deprecations without using ignoreDeprecations, since TypeScript 7 turns them into hard errors. Then install typescript@^7.0.2 and validate with tsc --noEmit, your build, and lint commands.
Use the official compatibility package with an npm alias: map @typescript/native to typescript@^7 and typescript to @typescript/typescript6. This exposes TypeScript 7 as tsc and TypeScript 6 as tsc6 for API-dependent tools.
No, TypeScript 7.0 does not expose a stable programmatic compiler API; the planned API target is TypeScript 7.1. Tools importing typescript, such as ts-morph or embedded-language plugins, should remain on TypeScript 6 until they add support.
Failures usually come from unresolved TypeScript 6 deprecations, which become errors in TypeScript 7, or from tooling that imports the old compiler API. Run tsc --noEmit on TypeScript 6 first, fix deprecations, and check dependencies for compiler-API consumers.
Embedded-language and Angular template tooling may still require TypeScript 6 until their plugin integrations support TypeScript 7. Keep those tools on TypeScript 6 via the compatibility package while using TypeScript 7 for direct type-checking.
Do not upgrade projects that must remain on TypeScript 5 or earlier, or tooling integrations that require a stable compiler API today. TypeScript 7 also assumes TypeScript 6 deprecations are resolved, so skip it if that cleanup is not feasible.
tachiiri-orgConfigure TypeScript compiler settings and baseline type-checking scripts.
IAG-PatternsGenerate a release readiness checklist covering documentation, CI, and rollback plans.
OpenClaudiaImplements next-intl internationalization with locale routing, hreflang sitemaps, and bulk translation for Next.js projects.
EdgeAppMigrate deprecated navigation type references for React Navigation v7 compatibility.