BREAKING CHANGE(TsBuild): Stop forcing emitDecoratorMetadata in protected compiler defaults
This commit is contained in:
@@ -1,5 +1,13 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-11-17 - 3.0.0 - BREAKING CHANGE(TsBuild)
|
||||
Stop forcing emitDecoratorMetadata in protected compiler defaults
|
||||
|
||||
- Removed emitDecoratorMetadata from the set of protected/critical default compiler options.
|
||||
- Projects that relied on tsbuild automatically enabling emitDecoratorMetadata (for DI frameworks like NestJS, TypeORM, Inversify) must now enable it explicitly in their tsconfig.json or via programmatic/CLI options.
|
||||
- No other protected defaults were changed; outDir, noEmitOnError, declaration and inlineSourceMap remain enforced.
|
||||
- Behavior is now more permissive: decorator metadata generation is controlled by user configuration rather than being forced by tsbuild.
|
||||
|
||||
## 2025-11-17 - 2.7.3 - fix(tsbuild.classes)
|
||||
Remove duplicate emitDecoratorMetadata from default compiler options and centralize it in protected defaults
|
||||
|
||||
|
||||
Reference in New Issue
Block a user