feat(twilio): emulate SendGrid mail with Gmail inspection - #226
Closed
kamal wants to merge 3 commits into
Closed
Conversation
Contributor
|
@kamal is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Applications can send email through their existing SendGrid clients and inspect the captured mail through the Google emulator's Gmail API, without a separate SMTP inbox service.
This extends the Twilio plugin rather than introducing a second email provider.
Design and limits
The official Node SDK resets its base URL in
setApiKey(), so configure the local endpoint afterward.HEAD metadata compatibility
The shared HTTP layer now finalizes HEAD responses with a null body while preserving response and middleware headers. An empty streamed body caused Bun to replace Content-Length with chunked encoding, leaving Ruby S3 download clients without the file size they need.
The fix applies with and without middleware and cancels any discarded response stream. It is separate from the earlier S3 binary-object work, which is not included in this PR.
Validation
partNumber=1.