typescript-v6

Configure and debug TypeScript 6+ projects with tsconfig guidance, compiler diagnostics, and migration patterns.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/brillianodhiya/VisionScript --skill typescript-v6-brillianodhiya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-v6
Source: https://github.com/brillianodhiya/VisionScript/tree/main/.agents/skills/typescript-v6
Command: npx skills add https://github.com/brillianodhiya/VisionScript --skill typescript-v6-brillianodhiya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, and includes references (resource) components.

What problem does it solve? Upgrading to or maintaining TypeScript 6+ projects often breaks builds through changed defaults, deprecated options like baseUrl and moduleResolution: "node", missing ambient globals, and shifted emit paths. This Skill provides release-note-grounded guidance to fix these regressions quickly instead of manually diffing documentation. ## Core Features & Use Cases - tsconfig Configuration: Set explicit rootDir, types, and modern moduleResolution (bundler vs nodenext) baselines for apps and Node packages. - Deprecation Migration: Replace deprecated baseUrl, ES5 targets, and legacy module settings, using ignoreDeprecations: "6.0" only as a temporary shield. - Compiler Diagnostics: Use tsc --showConfig, --explainFiles, and --traceResolution to verify config and resolution before editing code. - Use Case: After upgrading a repo to TypeScript 6, builds fail with "Cannot find name 'process'" and output shifts to dist/src/. Use this Skill to add explicit types and rootDir entries and verify the fix with tsc --noEmit. ## Quick Start Ask the AI to review your tsconfig.json for TypeScript 6 compatibility and fix any deprecated options or missing explicit settings.

Frequently Asked Questions about typescript-v6

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

FAQPage Schema
How do I migrate my tsconfig to TypeScript 6?▼

Make rootDir and types explicit, replace deprecated moduleResolution node with bundler or nodenext, and remove baseUrl in favor of direct paths entries. Use ignoreDeprecations "6.0" only temporarily while completing the migration, then verify with tsc --noEmit.

Should I use moduleResolution bundler or nodenext in TypeScript 6?▼

Use bundler for apps built with Vite, Rollup, esbuild, or Webpack, and nodenext for Node.js packages where package exports and ESM/CJS interop matter. TypeScript 6 deprecates the old node and node10 resolution modes.

Why does TypeScript 6 say Cannot find name 'process' or 'describe'?▼

TypeScript 6 projects should not rely on implicit ambient type discovery for Node or test globals. Add explicit types entries like ["node", "jest"] in tsconfig and install the matching @types packages.

Why is my TypeScript output going to dist/src instead of dist?▼

This happens when rootDir is inferred rather than explicit, a common TypeScript 6 upgrade regression. Set rootDir to ./src alongside outDir ./dist and include src/**/* to restore the expected emit layout.

Does TypeScript 6 support Temporal and RegExp.escape?▼

TypeScript 6 provides types for RegExp.escape via es2025 lib and Temporal via esnext typings, but compiler type support does not guarantee runtime availability. Verify your target runtime supports these APIs before shipping.

When should I use the stableTypeOrdering flag?▼

Use --stableTypeOrdering only when comparing TypeScript 6 and TypeScript 7 behavior or investigating ordering-sensitive inference issues. It adds type-checking overhead and is not intended for normal builds or CI defaults.