Gabriel Miranda

Should be fixed under [`@react-email/[email protected]`](https://github.com/resend/react-email/blob/canary/packages/tailwind/CHANGELOG.md#100-canary0), a breaking change because it requires you use `@react-email/render@>=1.0.0`

love this idea +1, for one of my project I had to make a hacky [mergeCallbacks](https://github.com/geiefi/Terraprisma/blob/master/packages/terraprisma/src/utils/mergeCallbacks.ts) for this sorta of stuff I wonder if it makes sense that this goes...

> +1 to just adding a bit of custom logic when needed I'd agree it's easier, but the problem with that is that you will have to override the handler...

Hey @ryansolid, thanks for the feedback. > We need to filter that out of prod via a dev check. Would a check on `isDev` be enough here (like bellow), or...

I also had this. Seems like, after a lot of debugging, this is being caused because the ref is set before the element is actually inserted into the DOM which...

@itsyoboieltr Here's a link for the support thread on Discord that others from the community helped me in fixing it https://discord.com/channels/722131463138705510/1215409288030330972

@beoxgame it's a bit of a long thread, the error might have a lot of causes, but in my situation it was my code rendering twice due to a bundler...

Hey @KSXGitHub > This is not your real problem, your real problem is that you want to use types-react in place of @types/react, correct? Sort of, yes. More specifically, it...

Oh, didn't know that. Thanks for the heads-up. Still, though, it resolves to a set version instead of the specifier: ```yaml [email protected]: dependencies: '@types/react': 18.3.3 ```

You are right, I misconfigured it again, sorry for not reading the docs thoroughly enough on this, but, the issue still seems to persist. Also, from the part of the...