npm / unplugin-dts
unplugin-dts
What changed in unplugin-dts 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.
1 breaking1 new APIs and options3 performance1 tooling25 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initunplugin-dts 131 changes
Breaking changes 1
forceDtsEmit was removed to support declarationMap.
New APIs and options 1
You can specify the module format for output.
Performance 3
Caches declaration module resolution.
Reduces build overhead.
Optimizes watch rebuilds.
Tooling 1
The tool automatically falls back to @typescript/typescript6 for TS 7+ compatibility.
Fixes and other changes 25
Preserves native declaration extensions in generated declarations.
Preserves the declaration graph across module formats.
Empty bundled entries are preserved.
Corrects module-resolution precedence in setModuleResolution.
Preserves typeof in static imports.
Stabilizes the Vue program lifecycle.
Separated publicRoot and entryRoot for TypeScript 6.0.
Relaxed the vue language core peer range, allowing compatibility with a wider range of versions.
Checks all aliases so a wildcard * does not block @/* resolution.
Fixes a getResolvedModule error when bundling dts files outside src.
Avoids a self-reference when the entry dts path equals the types path.
Adds the .js extension to synthetic entry imports for nodenext.
Declarations are re-emitted when non-type files change in watch mode.
Forwards aliasesExclude to Runtime.
Prevents optional peer types from leaking into declaration files.
Corrects the exported type for the Rolldown plugin.
Includes .vue files when resolving tsconfig include patterns.
Resolves API Extractor failures involving Vue internal types when bundleTypes is enabled.
Custom resolver files can pass through transform.
The default output directory is parsed from the scaffold.
The strategy for skipping insert index is stricter.
Aliases in namespace imports are handled correctly.
tsconfig globs are resolved relative to the tsconfig directory.
tsconfig paths without baseUrl are resolved relative to the config directory.
Vue files are auto-detected and the processor is set automatically.