[Nuxt] Updating from vue-emai to @vue-email/nuxt breaks email rendering about nuxt HOT 8 OPEN

Sure thing. Here you go

from nuxt.

yes, this is an issue we already know, importing things outside of what we already allow is not gonna work, nuxt works in a different way when the project is built, its one of the draw backs of the SSR solution we made, wil keep this open till we find a solution for that, we currenlty only auto import components that live on the emailsfolder and thats it

more info: https://vuemail.net/ssr/introduction

from nuxt.

@Flowko Thanks for the swift reply!

I was wondering, it works perfectly fine in the same setup using [email protected] and the vue-email/nuxt module in both development and with the build. I have reverted to that for now.

What caused the regression? Did anything change in newer releases of Vue/Nuxt?

from nuxt.

hmm interseting, would you be able to share a reproduction please, i would love to take a look, cus that shouldn't work haha

from nuxt.

@Flowko Did you have a chance to look at the reproduction? This is keeping me from updating my project dependencies. In order to update nuxt / vue I'd have to use a newer version of vue-email and remove all the type imports from my components. So it'd be good to know if you're planning on fixing this any time soon. Thanks!

from nuxt.

@juni0r ah sorry, yes im planning to work on it after i finish my full time project, sorry for the delay 🙏

from nuxt.

@Flowko I was testing on local the reproduction repo, I found some interesting things. It's like @juni0r says, in the v0.7.2, the types importations works, but in the newer versions not.

This "issue" is related to write/read permissions, but is not by the nuxt package, is a compiler issue.

from nuxt.

@Flowko I understand you have other priorities right now, but do you think there's a chance this is going to be fixed any time soon? It becomes increasingly difficult to manage project dependecies to accomodate v0.7.2. We're now left with the only alternative to refactor all email templates to not use type imports which is a bit of a bummer, but would enable us to upgrade. I don't mean to put pressure on this but I need manage expectations here.

Thank you!

from nuxt.