GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — TestBed.overrideComponent doesn't work with AOT and webpack · Issue #32628 · angular/angular-cli Open Labels area: @angular-devkit/build-angulardevkit/build-angular:karmafreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fix DescriptionCommandtest Is this a regression?
The previous version in which this bug was not present wasNo response DescriptionTestBed.overrideComponent and TestBed.overrideModule don't seem to work with karma, webpack builder (builderMode: browser) and aot enabled. Changing any of these settings, so builderMode: application or disabling aot "fixes" the problem. The same issue was reported here #30017 but i guess it was only fixed for esbuild? Is there any workaround for this? or can it be fixed for angular20? Minimal ReproductionCreate a simple valid component, turn on AOT for Karma, and make a test where you use TestBed.overrideComponent to reset metadata. You don't even need to specify an actual override in the second parameter to trigger the issue: TestBed.overrideComponent(YourComponent, {}) triggers the failure. builderMode: browser needs to be set Exception or ErrorYour EnvironmentAnything else relevant?No response Activity
MetadataMetadataAssigneesLabelsarea: @angular-devkit/build-angulardevkit/build-angular:karmafreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fix TypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |