Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    TypeScript 7 Upgrade: Fix Removed tsconfig Options, Changed Defaults and Tooling

    1

    Scans your repo, fixes every tsconfig option TypeScript 7.0 rejects or silently changes, sets up 6.x side by side for tools that need the compiler API, and checks the result with before/after type-check and emit diffs.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    TypeScript 7 Upgrade: Fix Removed tsconfig Options, Changed Defaults and Tooling

    TypeScript 7 Upgrade: Fix Removed tsconfig Options, Changed Defaults and Tooling

    Example session with this skill installed

    Upgrade our orders-api repo to TypeScript 7. It extends tsconfig.base.json, uses ts-jest and typescript-eslint, and builds to dist/.

    • Read your context and instructions
    • Compiled the typescript 7 upgrade

    TypeScript 7 Preflight (before fixes)

    • tsconfig files: 2 | BLOCKER 7 | HIGH 7 | INFO 1
    #SeverityWhereCodeFinding
    1BLOCKERsrc/index.ts:1IMPORT_ASSERTSImport "assert { ... }" is an error in 7.0
    2BLOCKERsrc/legacy/ns.ts:1MODULE_NAMESPACE"module" keyword used for a namespace
    3BLOCKERtsconfig.base.jsonTARGET_ES5"target": "es5" is a hard error
    4BLOCKERtsconfig.base.jsonMODULE_RESOLUTION"moduleResolution": "node" is a hard error
    5BLOCKERtsconfig.base.jsonDOWNLEVEL_ITERATIONremoved option
    6BLOCKERtsconfig.jsonBASE_URL"baseUrl" is a hard error
    7BLOCKERtsconfig.jsonPATHS_NON_RELATIVE"src/*" becomes TS5090 once baseUrl is removed
    8HIGHpackage.jsonAPI_CONSUMERts-jest / typescript-eslint need the 6.x compiler API
    9HIGHtsconfig.jsonTYPES_DEFAULTtypes now [] (installed: @types/express, @types/jest, @types/node)
    10HIGHtsconfig.jsonROOTDIR_DEFAULTrootDir unset with outDir: output may move to dist/src

    Verdict: NOT READY (exit code 2)

    TypeScript 7 Migration Report: orders-api

    Verdict: READY. Compiler 5.9 -> 7.0.2, install pattern B (6 + 7 side by side)
    Changes: target es2022; module/moduleResolution nodenext; removed baseUrl and downlevelIteration; paths "./src/*"; rootDir "./src"; types ["node"]; assert -> with; module -> namespace; @enum -> @typedef; "type": "module"; ./polyfills.js extension.
    Verification: npx tsc --version -> 7.0.2; npx tsc6 --version -> 6.0.3; tsc --noEmit -> 0 errors; emit layout flat (dist/index.js); preflight exit code 0.

    tsconfig.base.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    TypeScript 7.0, the native Go compiler, is much faster. It also breaks real projects in three ways that are easy to miss.

    1. Options removed in 7.0 now stop the build: baseUrl, moduleResolution: node/node10/classic, target: es5, downlevelIteration, AMD/UMD/System modules, and esModuleInterop: false.
    2. Defaults changed silently: types is now [], so Cannot find name 'process' appears. rootDir is now ./, so output can move to dist/src/. strict, module and target changed too.
    3. No compiler API in 7.0: typescript-eslint, ts-jest, ts-node, Vue, Svelte, Astro and Angular templates still need 6.x.

    This skill gives your agent a read-only preflight scanner (Python standard library only). The scanner follows extends chains and reports each problem once, in the file where it is set. It also flags paths targets that break once baseUrl is removed (TS5090), assert import attributes, module namespaces and old JSDoc forms. Your agent then follows a 7-step procedure: baseline, fix blockers base-first, pin the changed defaults, install 7.0 next to 6.x where needed, then verify with type-check counts, an emit-layout diff and a self-check. You get a migration report that someone can review.

    All facts were checked on 2026-11-07 against the official TypeScript 7.0 and 7.1 Beta announcements, then tested with tsc 7.0.2 (error codes TS5102, TS5108, TS5090, TS2880, TS1540, TS2749 and TS2856 are mapped to fixes).

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    Source scanning uses pattern matching, so it can flag matches inside comments or strings. It does not detect every JSDoc change (values used as types, standalone ?, postfix !); the tsc 7 type-check in step 6 catches those. extends targets in uninstalled packages are reported, not checked. The skill covers the 7.0 migration; TypeScript 7.1 (beta as of 2026-10-20) is described but treated as a separate step. It does not convert JavaScript to TypeScript or clean up type errors that existed before the upgrade.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    Software
    Python 3.8+Node.js
    npm
    orpnpm
    orYarn
    orBun
    Terminal accesstsctypescripttsc6

    Python runs the preflight scanner (standard library only). Node.js and a package manager run the type-check and install steps.

    Permissions

    Allowed Hosts

    registry.npmjs.org (only when the agent installs TypeScript packages)

    File Scopes

    tsconfig*.json
    package.json
    project
    source
    files
    (.ts
    .tsx
    .mts
    .cts;
    .js
    when
    allowJs
    is
    on)

    The bundled scanner is read-only and makes no network calls. File edits happen only in the fix steps, through your agent's normal edit tools, and never in node_modules.

    Listed10 days ago

    What's inside

    Frequently Asked Questions

    Every tsconfig option that TypeScript 7.0 rejects (baseUrl, node/node10/classic resolution, es5 target, downlevelIteration, AMD/UMD/System modules, interop and alwaysStrict set to false, stableTypeOrdering false), paths targets that turn into TS5090, the changed defaults (types, rootDir, strict, module, target, noUncheckedSideEffectImports, libReplacement), tools that need the compiler API, and source patterns such as assert imports, module namespaces and old JSDoc.

    It was checked on 2026-11-07 against the official TypeScript 7.0 (2026-07-08) and 7.1 Beta (2026-10-20) announcements, and tested with tsc 7.0.2 and the @typescript/typescript6 6.0.3 alias. Source links and dates are inside the skill.

    No. It detects tools that import the typescript package and sets up the official side-by-side install. tsc runs 7.0, while require('typescript') still resolves to 6.x until those tools support the new API.

    tsc 7 does not warn about silently changed defaults: a moved dist/src layout, dropped @types globals, or a new module format. It also does not tell you which base config to fix or how to keep API-based tools working. This skill covers all of that and checks the result with an emit diff and exit codes.

    Yes. Per the 7.0 announcement, it keeps their template type-checking on 6.0 and uses 7.0 for plain tsc builds.