feat(integrations): add Azure Communication Email integration example#3102
Open
rahulbhadja wants to merge 3 commits into
Open
feat(integrations): add Azure Communication Email integration example#3102rahulbhadja wants to merge 3 commits into
rahulbhadja wants to merge 3 commits into
Conversation
- Added documentation for Azure Communication Email integration. - Created example for sending emails using Azure Communication Email. - Updated integrations list and snippets to include Azure Communication Email.
|
Contributor
|
@rahulbhadja is attempting to deploy a commit to the resend Team on Vercel. A member of the Team first needs to authorize it. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
3 issues found across 8 files
Confidence score: 3/5
- There is a concrete regression risk around the new
beginSendflow: bothapps/docs/integrations/azure-communication-email.mdxandexamples/azure-communication-email/src/index.tsxomit an explicit production credential permission check, which could lead to failed sends or misconfigured deployments. - I’m scoring this as moderate merge risk because the top findings are medium-high severity (7/10) with high confidence (9/10), and they affect guidance and sample implementation that users are likely to copy.
examples/azure-communication-email/tsconfig.jsonis a smaller but real correctness issue: missing Node ambient types while usingprocess.envcan cause type errors and confusion in local builds.- Pay close attention to
apps/docs/integrations/azure-communication-email.mdx,examples/azure-communication-email/src/index.tsx, andexamples/azure-communication-email/tsconfig.json- permission-check guidance forbeginSendand Node typing should be fixed before broad adoption.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="examples/azure-communication-email/tsconfig.json">
<violation number="1" location="examples/azure-communication-email/tsconfig.json:21">
P2: Missing Node.js types in tsconfig.json while using `process.env` Node global. The `types` array only includes `vitest/globals`, excluding Node.js ambient types needed for `process.env` usage in `index.tsx`. Add `@types/node` to the types array to ensure proper type-checking.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "lib": ["ESNext", "DOM", "DOM.Iterable"], | ||
| "module": "ESNext", | ||
| "target": "ESNext", | ||
| "types": ["vitest/globals"], |
Contributor
There was a problem hiding this comment.
P2: Missing Node.js types in tsconfig.json while using process.env Node global. The types array only includes vitest/globals, excluding Node.js ambient types needed for process.env usage in index.tsx. Add @types/node to the types array to ensure proper type-checking.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At examples/azure-communication-email/tsconfig.json, line 21:
<comment>Missing Node.js types in tsconfig.json while using `process.env` Node global. The `types` array only includes `vitest/globals`, excluding Node.js ambient types needed for `process.env` usage in `index.tsx`. Add `@types/node` to the types array to ensure proper type-checking.</comment>
<file context>
@@ -0,0 +1,25 @@
+ "lib": ["ESNext", "DOM", "DOM.Iterable"],
+ "module": "ESNext",
+ "target": "ESNext",
+ "types": ["vitest/globals"],
+ },
+ "include": ["."],
</file context>
Contributor
There was a problem hiding this comment.
Thanks for confirming!
gabrielmfern
requested changes
May 18, 2026
Member
gabrielmfern
left a comment
gabrielmfern
left a comment
There was a problem hiding this comment.
it should be using react-email not @react-email/components
| <CodeGroup> | ||
|
|
||
| ```sh npm | ||
| npm install @azure/communication-email @react-email/components |
Member
There was a problem hiding this comment.
Suggested change
| npm install @azure/communication-email @react-email/components | |
| npm install @azure/communication-email react-email |
| ``` | ||
|
|
||
| ```sh yarn | ||
| yarn add @azure/communication-email @react-email/components |
Member
There was a problem hiding this comment.
Suggested change
| yarn add @azure/communication-email @react-email/components | |
| yarn add @azure/communication-email react-email |
| ``` | ||
|
|
||
| ```sh pnpm | ||
| pnpm add @azure/communication-email @react-email/components |
Member
There was a problem hiding this comment.
Suggested change
| pnpm add @azure/communication-email @react-email/components | |
| pnpm add @azure/communication-email react-email |
|
|
||
| ```tsx email.tsx | ||
| import * as React from 'react'; | ||
| import { Html, Button } from "@react-email/components"; |
Member
There was a problem hiding this comment.
Suggested change
| import { Html, Button } from "@react-email/components"; | |
| import { Html, Button } from "react-email"; |
|
|
||
| ```tsx | ||
| import { EmailClient } from '@azure/communication-email'; | ||
| import { render } from '@react-email/components'; |
Member
There was a problem hiding this comment.
Suggested change
| import { render } from '@react-email/components'; | |
| import { render } from 'react-email'; |
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
3 participants
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
Adds new Azure Communication Email integration example to React Email.
Changes
Notes
@azure/communication-emailAZURE_EMAIL_CONNECTION_STRINGSummary by cubic
Adds an Azure Communication Email integration example and docs. Lets users render with
@react-email/componentsand send via@azure/communication-emailusingAZURE_EMAIL_CONNECTION_STRING.examples/azure-communication-emailshowing render +EmailClient.beginSend(polished with single quotes and cleanedtsconfig).Written for commit 7ac0008. Summary will update on new commits.