fix(@react-email/tailwind): Stop inlining JSX runtime #1462
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@eps1lon is attempting to deploy a commit to the resend Team on Vercel. A member of the Team first needs to authorize it. |
huozhi
approved these changes
May 13, 2024
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.
Current builds of
@react-email/tailwindhave the JSX runtime inlined (see occurences ofReactCurrentOwnerin https://unpkg.com/@react-email/[email protected]/dist/index.js). It should be treated as an external package just likereactandreact-dom. Otherwise it may break between any release since React packages need to be used in lockstep. However, inlining the JSX runtime could mean that a consumer has 18.3 installed, while the library was published with an inlined version of 18.2