-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(@angular/build): handle external @angular/
packages during SSR
#29094
Conversation
99c9f1a
to
ee15370
Compare
This commit introduces `ngServerMode` to ensure proper handling of external `@angular/` packages when they are used as externals during server-side rendering (SSR). Closes: angular#29092
ee15370
to
e2d52fb
Compare
const source = await javascriptTransformer.transformFile(filePath); | ||
let source = await javascriptTransformer.transformFile(filePath); | ||
|
||
if (filePath.includes('@angular/')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if the name does not include '@angular/'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ngServerMode
is not added. And the resolved module will be returned with the standard transformations.
packages/angular/build/src/utils/server-rendering/esm-in-memory-loader/loader-hooks.ts
Outdated
Show resolved
Hide resolved
…ng SSR Co-authored-by: Charles <19598772+clydin@users.noreply.github.com>
The changes were merged into the following branches: main, 19.0.x |
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. |
This commit introduces
ngServerMode
to ensure proper handling of external@angular/
packages when they are used as externals during server-side rendering (SSR).Closes: #29092