Replace Vite after wasp gen?
After wasp generates all my files, is it possible to replace Vite with Next manually in a way that doesn't break
wasp start?5 Replies
Wasp recompiles the code in
.wasp on each source change. If you were to adjust the code in .wasp to use Nextjs, this would mean you can't use Wasp any more 😦
@Zeko369 might be able to give you some unique insight about hacking Wasp@Baps Hm, why do you think you need to do this? In other words, what do you need from Next? Maybe we can help you get it in a simpler way
@miho @Filip I'm learning new web dev stuff, and all the tutorials use Next. Also love how Next handles images with
Image.
So there's too much friction at the moment with Vite errors. I tried using Primereact in Next which was a breeze but harder to integrate in Next.
I think you mentioned Wasp will add support for Next sometime, it'd be great to see that. Too many devs, tutorials, apps invested in Next for Next to be ignored.In that case, I recommend you change how you approach this thing 😄
As Miho said, adding Next to Wasp is not possible nor do we have plans to do it.
It's not really how these two technologies were meant to work.
Adding Next to Wasp because many tutorials use it is like trying to learn cooking while having an electric stove at home, seeing that most cooking tutorials use a gas/fire stove, and then trying to make your electric stove light up a fire and pump gas to simulate a gas stove.
A weird analogy, but I think it fits 😄
Anyway, if you're learning web dev, I suggest you focus on the fundamentals - JavaScript, then React/Vue, and then Wasp or Next.
Not all web dev tutorial use Next - far from it!
Next is just one of the many high-level frameworks and sits on the same level as Wasp - these aren't meant to be used together. You pick one and use that (but ideally after you learn the fundamentals).
Next does some of the stuff Wasp can't do (e.g., great SSR support), while Wasp does other stuff that Next can't do (e.g., out of the box full-stack functionalities).
After you learn the fundamentals (Js, React, etc), you'll know which one is a better fit for what you're trying to build.
Hope this helps!
That's great feedback and suggestions! Thank you. I'll rethink my approach.