fix(ivy): remove debug utilities from ivy production builds (#30130)
Prior to this commit, we were pulling DebugNode and DebugElement into production builds because BrowserModule automatically pulled in NgProbe and thus getDebugNode. In Ivy, this is not necessary because Ivy has its own set of debug utilities. We should use these existing tools instead of NgProbe. This commit adds an Ivy switch so we do not pull in NgProbe utilities when running with Ivy. This saves us ~8KB in prod builds. PR Close #30130
This commit is contained in:

committed by
Andrew Kushnir

parent
f45684ff95
commit
71b8b355a6
@ -18,3 +18,5 @@ export {DomSanitizer, SafeHtml, SafeResourceUrl, SafeScript, SafeStyle, SafeUrl,
|
||||
|
||||
export * from './private_export';
|
||||
export {VERSION} from './version';
|
||||
// This must be exported so it doesn't get tree-shaken away prematurely
|
||||
export {ELEMENT_PROBE_PROVIDERS__POST_R3__ as ɵELEMENT_PROBE_PROVIDERS__POST_R3__} from './dom/debug/ng_probe';
|
||||
|
Reference in New Issue
Block a user