Respect tsconfig's "paths" option? #129
Replies: 3 comments 7 replies
-
Is this strictly with the preview app, or does that happen with |
Beta Was this translation helpful? Give feedback.
-
I have a working solution for this and will be posting a PR shortly. Will tag you in that. |
Beta Was this translation helpful? Give feedback.
-
I have tried using jsx-email. "The general guidance there is that email templates shouldn't be reusing client components because client components aren't written for email, and the requirements are vastly different." Using them as is - is not possible because of transitive imports. Blocking and preventing the usage of one of the most common absolute import alias "@" in any project wanting to use jsx-email does not seem like a good idea. |
Beta Was this translation helpful? Give feedback.
-
I'm a react-email refugee and I'm having some trouble. (First, it'd be great if there was a react-email migration guide!)
I have the following in my project's tsconfig.json:
JSX email doesn't like having
@/
in my import statements. Even though I can replace those with../
, the preview still gives me "Failed to load url" errors for everyimport from '@/…'
in my imported components.I dread the idea of going through my entire project to replace the
@/
imports with relative paths. Is there a way to work around this in JSX email?Beta Was this translation helpful? Give feedback.
All reactions