do I need vike?
Mostly for my learning, I had this doubt about how https://vike.dev and Wasp share similarities or differences? For example, I know Vike provides easy routing, and so does Wasp. Is it meant to be used along with Wasp? I know it was recommended here in this Discord when it was called vite-plugin-ssr or something like that. Now it's called Vike.
Vike
Like Next.js/Nuxt but as do-one-thing-do-it-well Vite plugin.
7 Replies
Hi @Baps. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry for the confusion, but there seems to be a misunderstanding. Wasp uses Vite, not Vike, as its build tool of choice. Vite is used to serve the client during development and for bundling it for production. You can customize the Vite config by editing the
vite.config.ts file in your project root directory. Wasp will use your config and merge it with the default Wasp's Vite config source (https://wasp-lang.dev/docs/project/custom-vite-config).
In the context of Wasp, Vite is used to set up Single Page Applications (SPAs). However, SPAs can have problems with SEO because everything is JavaScript, not much actual HTML gets delivered to robots. Wasp allows you to go a bit faster in certain scenarios handling boilerplate setup and gives you some niceties out of the box, which is mainly great for developer experience, but for SEO not so much due to no fault of Wasp but the nature of SPA source (https://discord.com/channels/686873244791210014/1219684155072184440).
As for Vike, it seems to be a different tool altogether and is not mentioned in the provided knowledge sources. Therefore, I can't provide any specific information about how it relates to Wasp. If you have any more questions about Wasp, feel free to ask!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Baps, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hey hey! Vike is a framework, Wasp is a framework 🙂 When you develop full stack apps you can pick only one framework inside of which you decide to build your app.
When we talked about the
vite-plugin-ssr, we wanted to use their great SSR tooling to some degree to maybe base Wasp's routing on top off.
So this is something that we as framework authors can integrate for you, the framework user 🙂 We still haven't tackled the problem of SSR, Vike might be a solution for us, it might not, we have to research and see which tools gives us the best DX 🙂Thanks @miho ! That is good to know!
Yup, thanks for sharing this @Baps , actually it sounds like Vike could be an interesting thing for us to use to bring SSR and similar capabilities to Wasp. We will have to look into it! But yeah, we might use it potentially.
They have this "Build your own framework" link (https://vike.land/), this could be interesting.
Came across this thread but to throw my two cents in, I'd love for there to be a wasp SSR solution to pre-render some chosen routes.
Hey @donmackinnon, thanks for the feedback! I've added your message to the relevant issue: https://github.com/wasp-lang/wasp/issues/1944
GitHub
Provide better direct support for static content in Wasp · Issue #1...
We have some users that have content heavy apps: often it is a combo of an app and a blog of some kind (e.g. educational content). While we currently advise to use Wasp + something like Astro, this...
🙏