martinsos Comments - Answer Overflow

Topics

martinsos

•Created by Leonardo Schwartz on 2/21/2025 in #🙋questions

Why prisma instead of drizzle?

Btw in the next month we plan to do a lot of brainstorming, and one part of it will be on Wasp's modularity and extensibility, of which one part will be these abstractions (especially Auth and Database since those are the clearest at the moment). So if it goes as we are planning right now, you can expect us sharing more info on our plans there, and we will likely also be asking community to chime in with their ideas, would be great to have you part of discussion there. As for Drizzle vs Prisma, @Leonardo Schwartz I am curious because I don't know that much about Drizzle except for basics, where do you find Prisma is lacking the most?

16 replies

•Created by Leonardo Schwartz on 2/21/2025 in #🙋questions

Why prisma instead of drizzle?

@Leonardo Schwartz , thanks for the input! It is awesome to hear that you read our articles, I often wonder how much people read about our vision :). As a person that chose Prisma years ago :), I can confirm what @Fecony and @miho said -> Drizzle didn't even exist back then (at least I had no idea about it). As for our vision of being stack agnostic vs tying ourselves to Prisma -> you are right in a way, but also what @Fecony wrote is very correct. I will put it this way: We on purpose decided to go with specific technologies for now (React, Node, Prisma, Postgres) in order to limit our "battle front". If we make Wasp work as we want it to for this set of technologies, it is not hard to imagine it working also for Vue next to React, Bun or Deno next to Node, Drizzle next to Prisma, MySQL next to Postgres. Ok, that depends how much we tie in conceptually into these technologies, if we are super relyant on very core concept of Prisma that no other solution does then that would be an issue -> but we are being quite careful about it, even if that is not obvious from the outside immediately. We are not super heavily relying on specific parts of any of these technologies that you won't see anywhere else. Even Prisma's DSL/schema -> we had our our db model DSL that was Prisma-agnostic and we will probably bring it back, we put it aside for now to focus on other stuff. We are instead really trying to focus on being glue in between them. Not like Blitz that was based on NextJS, or Meteor that had one of main features rely on unique capabilities of minimongo. Pinning down some of the tech in Wasp gives us space to focus on innovating on some other parts that we want to focus on now, till we get those down. To go back to what I said -> we are making sure not to tie in too much conceptually. But, we gave ourselves some leeway to tie in implementation-wise, meaning that right now, Prisma is not an implementation of a DB interface/abstraction defined on Wasp level: instead it is indeed integrated directly with it. Why not immediately design a proper DB abstraction layer that Prisma is just one implementation of, so that we are truly agnostic? And also do similar for React as frontend library for example? Beacuse we didn't want to get ourselves entangled into guessing what this abstraction should be and then constantly fighting it, when we don't know really know enough yet -> we wanted to start with something, learn on the way, and then when we are smarter, figure out the proper abstraction. I don't think anybody can say for sure what is the right way -> sometimes, it does make sense to start with abstraction first, and I have often done that in other projects, but I always had a better idea of the domain and abstractions were simpler. So here, I prefer the approach of implementing IMPL1, then when you want to add IMPL2, is the time to look for common abstraction. Danger is that you get do tied up to IMPL1 that introducing abstraction layer becomes very tough, but I think we do have enough knowledge to have avoided that mostly. On the other hand, I don't we had enough konwledge to get the abstraction right from the first go, or even right enough, to not be PITA. As @Fecony said, we expect Wasp to evolve in the sense that more and more of these abstractions crystalize. If I had to guess which ones are coming first, I would say Auth and Database. Entities also -> right now they are always DB models, but they could be more. I am sorry I can't give more concrete answers, but TL;DR: You are right we are somewhat tied in impelmentation-wise, but it's not as much as it might seem, and we are careful about it, especially not to tie in too much conceptually-wise. We are in the background planning for those abstractions, and they will be coming.

16 replies

•Created by Justin Williams on 2/15/2025 in #🙋questions

WSL Install Errors: EISDIR & symlink

@Justin Williams it seems this was about the permissons in the WSL, but it is hard for me to say what exactly it was. Glad to hear you got it going though! It would help if you could maybe figure out what changed on yoru second attempt -> what might have you deleted or done differently that enabled it to work then?

8 replies

•Created by p4j4r5 on 1/29/2025 in #🙋questions

SEO issue . Twitter or facebook cannot recognise meta tags

My bad I haven't read the whole convo here! Ok, I wasn't aware that helmet-async doesn't work in that case. Actually let's try to be systematic here. @NEROX , I remember you said some time ago that you had good success with react-helmet-async, for meta tags, right? Is that still correct? On the other hand, you say now that it doesn't work for the opengraph (og) images -> so is that a "special" case of when it doesn't work, or does it also not work for other meta tags then? The question is also, why doesn't it work? Because the parsers that parse opengraph images don't wait for JS to render? As for solutions -> yeah, React 19 might already solve it for us, if not, then SSR is the way to go. We will be adding both to Wasp in the upcoming time, but I can't promise exactly when yet.

25 replies

•Created by p4j4r5 on 1/29/2025 in #🙋questions

SEO issue . Twitter or facebook cannot recognise meta tags

Yup https://github.com/wasp-lang/wasp/issues/1910 is a good read with all th elinks from it, specifically usage of react-helmet-async

25 replies

•Created by Andrea on 10/6/2024 in #🙋questions

Refresh token is null

Awesome @witczax glad to hear!

20 replies

•Created by RichardHpa on 3/10/2024 in #🙋questions

Can I split up the main.wasp file into seperate files

Oh interesting somebody showed on Medium how they split Wasp TS config into multiple fiels! I will summon @Filip , who wrote Wasp TS Config and will answer this the best :).

31 replies

•Created by chilled_techie on 1/2/2025 in #🙋questions

Disable Database

Yes maybe! Grand vision is that entities are not db-specific -> instead, they are piece of state that is important for your app through full-stack, and they can be persisted in the database, or coming from Twitter API, or something completely else. So vision is that Entities are standalone concept with different backends/resolvers. But, not there yet. For now, I don't know what makes most sense hm -> maybe what you said Filip, something like "I know what I am doing". Or just accepting that we don't yet support non-db use cases and continue with it a bit longer, although I can understand why that can be frustrating.

15 replies

•Created by cmcglynn on 12/4/2024 in #🙋questions

How can I edit the Auth login/logout screens?

I put it back on triage so we can potentially prioritize it

11 replies

•Created by cmcglynn on 12/4/2024 in #🙋questions

How can I edit the Auth login/logout screens?

Oh actually we have an issue for this, it is missing in docs indeed! Uff we should add this https://github.com/wasp-lang/wasp/issues/1438

11 replies

•Created by cmcglynn on 12/4/2024 in #🙋questions

How can I edit the Auth login/logout screens?

It should be in the docs, you can write your own Login Form that uses actions that Wasp provides, but I do admit it is harder to find in docs than I expected hm! I found it for Username and pass here: https://wasp-lang.dev/docs/auth/username-and-pass#1-using-the-signup-and-login-actions . But I actually failed to find it for Email method. Is it possible that this is not doable for email and pass method @miho ? Or we forgot to document it?

11 replies

•Created by genyus on 12/16/2024 in #🙋questions

Accessing static files

Oh yes! Or in JS, not TS specific.

19 replies

•Created by Obaydah on 12/9/2024 in #🙋questions

Error when running migrate-dev

And thanks for pinging us!

20 replies

•Created by wardbox on 12/17/2024 in #🙋questions

Github Auth callback url fly

@miho might be able to give some human help here

74 replies

•Created by Sam Jakshtis on 12/16/2024 in #🙋questions

Facebook login?

Here is an example of user adding support for Discord, you might be able to copy that in big part: https://github.com/wasp-lang/wasp/pull/2110 ! THere is also an example of impelmenting a custom auth provider (Spotify): https://gist.github.com/infomiho/3c63de7d53aba59d6293bcb59501a029

6 replies

•Created by Killshot on 12/9/2024 in #🙋questions

LemonSqueezy webhooks not working after deployment (VPS)

Hm that means logs are getting lost somewhere? Is it possible you are not running the latest code btw? Or maybe you need to make sure those logs surface out, maybe the Docker logs you are looking at the moment are not showing them but only errors or something like that?

81 replies

•Created by Navita on 12/15/2024 in #🙋questions

I am customizing the SaaS template

If you are please check instructions here https://wasp-lang.dev/docs/quick-start#installation-1, under Windows.

10 replies

•Created by utomoo on 12/14/2024 in #🙋questions

Usemage app result show blank white screen

Yup those are just issues in the genreated code! Mage makes mistakes easily.

8 replies

•Created by genyus on 12/5/2024 in #🙋questions

Broken generator

@genyus ok thanks for letting us know!

14 replies

•Created by Bruno Njeru on 12/13/2024 in #🙋questions

user context

Code for that button is avaliable to you, so you can just change it!

6 replies