Repository navigation
Output bundle import map integrity key warning in browser #33617
Description
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
When building an app now, I see warnings in the browser. This is the importmap for the lazily loaded chunks. The warning indicates that the keys for the hashes are not valid. It seems that they should be a valid url, e.g. starting with ./, / etc, but they aren't.
The warning message is something like this:
Ignored an import map value of "chunk-2CJiPTcF.js": Integrity key is not a valid absolute URL or relative URL starting with '/', './', or '../'
If I examine the generated index.html, I see on top of the head section the importmap, where this json content is set. It looks like this:
My guess is, that they should simply have a prepending ./ before the keys, e.g. ./chunk-2CJiPTcF.js instead of simply chunk-2CJiPTcF.js. If I add it manually after the build, the warning disappears.
Is it a bug?
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Ignored an import map value of "chunk-SYbG1sRo.js": Integrity key is not a valid absolute URL or relative URL starting with '/', './', or '../'
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 22.0.7
Angular: 22.0.7
Node: 24.16.0
Package Manager: yarn 4.17.1
OS: macOS Tahoe 26.5.2
Anything else?
No response
Activity
fix(@angular/build): ensure import map integrity keys are valid URL-l…
fix(@angular/build): ensure import map integrity keys are valid URL-l…
fix(@angular/build): ensure import map integrity keys are valid URL-l…
fix(@angular/build): ensure import map integrity keys are valid URL-l…
fix(@angular/build): ensure import map integrity keys are valid URL-l…
fix(@angular/build): ensure import map integrity keys are valid URL-l…
angular-automatic-lock-bot commentedon Aug 21, 2026
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.