Skip to content

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Oct 10, 2024

Some cloud providers, such as Cloudflare, expect the default export to follow a specific structure (e.g., an object with a fetch property). To prevent the need for creating a separate server.ts file for production builds, the request handler is now exported as reqHandler instead of a default export.

@alan-agius4 alan-agius4 requested a review from dgp1130 October 10, 2024 10:21
@alan-agius4 alan-agius4 added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release labels Oct 10, 2024
@alan-agius4 alan-agius4 force-pushed the req-handler branch 3 times, most recently from 92aed2d to cf18cdd Compare October 10, 2024 12:00
@alan-agius4 alan-agius4 requested review from clydin and removed request for dgp1130 October 10, 2024 12:00
@alan-agius4 alan-agius4 force-pushed the req-handler branch 3 times, most recently from 283b018 to f0460bf Compare October 10, 2024 12:59
@alan-agius4 alan-agius4 changed the title fix(@angular/build): use named export handler for server.ts request handling fix(@angular/build): use named export reqHandler for server.ts request handling Oct 10, 2024
…est handling

Some cloud providers, such as Cloudflare, expect the default export to follow a specific structure (e.g., an object with a `fetch` property). To prevent the need for creating a separate `server.ts` file for production builds, the request handler is now exported as `reqHandler` instead of a default export.
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 10, 2024
@alan-agius4 alan-agius4 merged commit bfa8fec into angular:main Oct 10, 2024
29 checks passed
@alan-agius4 alan-agius4 deleted the req-handler branch October 10, 2024 20:20
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: @angular/build target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants