angular: Defer blocks export default regression after upgrading to v17.2
Which @angular/* package(s) are the source of the bug?
compiler-cli
Is this a regression?
Yes
Description
I get an error on runtime that type is undefined. It happens in a page that uses the defer block. If I revert the upgrade it works fine. I think it’s related to the compiler cli package.
export function getComponentDef<T>(type: any): ComponentDef<T>|null {
return type[NG_COMP_DEF] || null;
}
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
No response
Anything else?
No response
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 18 (6 by maintainers)
Commits related to this issue
- fix(compiler-cli): use correct symbol name for default imported symbols in defer blocks This commit addresses a problem with PR #53695 that introduced support for default imports, where the actual dy... — committed to JoostK/angular by JoostK 4 months ago
- fix(compiler-cli): use correct symbol name for default imported symbols in defer blocks This commit addresses a problem with PR #53695 that introduced support for default imports, where the actual dy... — committed to JoostK/angular by JoostK 4 months ago
- fix(compiler-cli): use correct symbol name for default imported symbols in defer blocks (#54495) This commit addresses a problem with PR #53695 that introduced support for default imports, where the ... — committed to angular/angular by JoostK 4 months ago
- fix(compiler-cli): use correct symbol name for default imported symbols in defer blocks (#54495) This commit addresses a problem with PR #53695 that introduced support for default imports, where the ... — committed to dgp1130/angular by JoostK 4 months ago
Yes, I can confirm it’s some regression when using export default.