Some General Questions
Hello,
I have just stumbled upon Wasp recently, i must say it looks awsome and promising. Being an experienced full stack software engineer i have few questions.
1. How easy it is to shift to any newer version of Node.js or any other dependencies involved which creates the biolerplate code?
2. Do we have any option to use Fastify instead of Express?
3. Is it coming out of the box with localization support on front-end?
4. Which part of code i don't need to touch or change in order to upgrade to newer version of Wasp?
5. Do we have any other full-stack example app developed with Wasp other than default TodoApp, it would have been nicer to create something a bit complex than using traditional TodoApp as an example.
6. what are the examples of adding custom logic to backend or frontend code?
I would really appreciate if someone from the core team of Wasp answer these questions.
Thanks
4 Replies
Hi @Irshad Ali. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hello,
I'm glad to hear you're interested in Wasp! Let's go through your questions:
1. Wasp is designed to handle the complexity of connecting all parts of the stack (client, server, database, deployment) together. It uses React, Node.js, and Prisma under the hood. However, the specifics of upgrading Node.js or other dependencies are not explicitly mentioned in the provided sources. You might want to check the official Wasp documentation or their Github repository for more details.
2. The provided sources do not mention the option to use Fastify instead of Express. Wasp is built with specific technologies under the hood, including Express. For more specific customization options, I recommend reaching out to the Wasp community or checking their official documentation.
3. Localization support is not mentioned in the provided sources. You might want to check the official Wasp documentation or their Github repository for more details.
4. Wasp's core feature is its compiler, which takes the Wasp config and your Javascript code and outputs the client app, server app, and deployment code. This means you define your app in the Wasp config and the compiler takes care of the rest. As Wasp updates, so does your app. However, the specifics of which parts of the code you don't need to touch during an upgrade are not explicitly mentioned in the provided sources.
5. The provided sources mention a Todo App tutorial, which takes you through all the core features of Wasp. For more complex examples, you might want to check the official Wasp documentation, their Github repository, or ask in their Discord community.
6. Custom logic can be added to both the backend and frontend of your Wasp app. However, the specifics of how to do this are not provided in the sources. You might want to check the official Wasp documentation or their Github repository for more details.
I hope this helps! For more detailed answers, I recommend reaching out to the Wasp community on Discord (https://discord.gg/rzdnErX) or checking their Github repository (https://github.com/wasp-lang/wasp). You can also subscribe to their newsletter (https://wasp-lang.dev/#signup) for updates.
Sources:
- Wasp Introduction (https://wasp-lang.dev/docs)
- Wasp Quick Start (https://wasp-lang.dev/docs/quick-start#installation)
- Wasp Tutorial (https://wasp-lang.dev/docs/tutorial/auth#whats-next)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
It doesn't answer my questions properly.
Hey, we usually don't work over the weekend, but here we are now 😄 let me try answering the questions
How easy it is to shift to any newer version of Node.js or any other dependencies involved which creates the biolerplate code?Wasp has some deps it keeps pinned e.g. the version of React Router, Prisma and React Query - but any other dep you are free to install any version and upgrade as you see fit. For Node.js we only have a lower limit i.e. it needs to be Node.js 18 or above, so 20, 22 are supported as well.
Do we have any option to use Fastify instead of Express?Currently Express is a hard dep of Wasp and you can't really swap out that bit. In the future we might go for Fastify as our backend base or even offer swapability - but not at this time, we are looking to create a stable package that works well and Express is the tool of choice atm 🙂
Is it coming out of the box with localization support on front-end?Not yet! We have it planned to add at some point since it's quite useful and requested feature: https://github.com/wasp-lang/wasp/issues/2061
Which part of code i don't need to touch or change in order to upgrade to newer version of Wasp?I'd recommend checking out our migrations guides between various Wasp versions to get a feel for it: https://wasp-lang.dev/docs/migrate-from-0-13-to-0-14 but generally, it's just some bit of your code, you don't usually touch stuff like the client<>server communication, auth, async jobs etc.
Do we have any other full-stack example app developed with Wasp other than default TodoApp, it would have been nicer to create something a bit complex than using traditional TodoApp as an example.The big one is https://opensaas.sh/ I think you'll like that one!
what are the examples of adding custom logic to backend or frontend code?Check out Open SaaS and our tutorial and that should be enough to answer your questions 🙂
Migration from 0.13.X to 0.14.X | Wasp
This guide only covers the migration from 0.13.X to 0.14.X. If you are migrating from 0.11.X or earlier, please read the migration guide from 0.11.X to 0.12.X first.
Open SaaS
Free, open-source SaaS boilerplate starter for React & NodeJS.
@miho thank you very much for your detailed response, really appreciated.