@rollup/plugin-typescript - Support for TypeScript 7 #2016

Activity

1. Khoeckman commented on Jul 20, 2026

   

   Khoeckman

   on Jul 20, 2026

   More actions

   C:\Users\kyleh\PP_FILE_STORE\packz_ai_assistant>npm run build
   
   > packz-ai-assistant-cloudflow@0.0.1 build
   > rollup -c
   
   [!] TypeError: Cannot read properties of undefined (reading 'ES2015')

   I can no longer build my code because of @rollup/plugin-typescript not supporting "typescript": "^7.0.2". Forcing me to stay on TS6
2. geggo98

   added a commit that references this issue on Jul 26, 2026

   build(deps): stop proposing TypeScript majors, and say when to stop i…

   ...

   b000f49
3. lwmacct commented on Aug 5, 2026

   

   lwmacct

   on Aug 5, 2026

   More actions

   I reproduced the failure with @rollup/plugin-typescript@12.3.0 and typescript@7.0.2:

   TypeError: Cannot read properties of undefined (reading "ES2015")
   

   The immediate cause is that TypeScript 7 exposes only version metadata from the typescript package root, while the plugin eagerly imports that package and reads ModuleKind at module scope.

   Changing the import to typescript/unstable/sync would not provide full compatibility. The new API exposes ModuleKind, but it does not expose several legacy APIs currently used by the plugin, including:

   • createWatchProgram
   • createWatchCompilerHost
   • createEmitAndSemanticDiagnosticsBuilderProgram
   • parseJsonConfigFileContent
   • sys
   • program.emit

   The missing programmatic emit functionality is being tracked upstream:

   • Add ability to get emit output from the API microsoft/TypeScript#63851
   • Add native-preview API for capturing .d.ts emit output microsoft/TypeScript#63843
   • API feature roadmap microsoft/TypeScript#63875

   I also tested the official TypeScript 7 and TypeScript 6 side-by-side dependency layout in a real Rollup project:

   {
     "devDependencies": {
       "@typescript/native": "npm:typescript@^7.0.2",
       "typescript": "npm:@typescript/typescript6@^6.0.2"
     }
   }

   The verification results were:

   • pnpm exec tsc --version reports 7.0.2
   • importing typescript provides the TypeScript 6 Compiler API, including ModuleKind and createWatchProgram
   • pnpm typecheck passes using TypeScript 7
   • pnpm build passes using the TypeScript 6 Compiler API through @rollup/plugin-typescript

   This is a working migration path, but it is not native TypeScript 7 support.

   There also appears to be a related issue with the documented custom typescript option from microsoft/typescript-go#2012: eager imports of the default typescript package prevent that option from cleanly selecting @typescript/typescript6 when typescript@7 is installed under its normal package name.

   Would the maintainers accept a short-term PR that:

   1. detects TypeScript 7 and reports an actionable compatibility error;
   2. documents and tests the official side-by-side setup;
   3. consistently uses the supplied compiler instance where possible;
   4. tracks full native support separately until the TypeScript 7 emit APIs are available?
4. stefgo

   added a commit that references this issue on Aug 17, 2026

   ci: Narrow the TypeScript hold to 7.x

   ...

   98b1400
5. lucavb

   added a commit that references this issue on Sep 30, 2026

   chore(deps): update dependency typescript to v6

   ...

   ec5aa6a