fix(@angular/build): only use external packages for polyfills when no local files are present#32761
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adjusts the polyfill bundling process. A new isLocalFile helper function is introduced to determine if a polyfill entry is a local file path. When a local file is detected among the polyfills, external package resolution is disabled for the polyfills bundle. This forces all polyfills, whether local or from packages, to be bundled together, which preserves their specified execution order. When no local files are in the polyfills list, the behavior respects the configured externalPackages option.
clydin
added
the
action: review
alan-agius4
added
action: merge
… local files are present The polyfills bundle now conditionally employs external package resolution only if no local files are detected in the polyfills array. If local files are present, all polyfills are bundled together to ensure the import execution order is correctly preserved between local and package-based entries.
clydin
force-pushed
the
application/selective-polyfill-bundling
branch
from
7aa477c to
78649ae
Compare
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
2 participants
The polyfills bundle now conditionally employs external package resolution only if no local files are detected in the polyfills array. If local files are present, all polyfills are bundled together to ensure the import execution order is correctly preserved between local and package-based entries.