Filip Sodić

Sure @piffio, thanks!

Hey @piffio, since we'd like to get this fix out as soon as possible, I was wondering whether you'll have time to finish it this week or should I take...

Thanks for the fast reply! No problem, I know how these things go :) Ok then, I'll take it off your hands.

The existing code works for now, although our extension story definitely could use some cleaning. This is covered by https://github.com/wasp-lang/wasp/issues/2222 and https://github.com/wasp-lang/wasp/issues/2385

Bumping this because it's requested a lot (@JakeLo123 also requested it again on a call today😄). Thanks for the patience, Jake!

Another user asking for this: https://discord.com/channels/686873244791210014/1348860456319586438/1348860456319586438

@InsOpDe Can you please explain in detail what happened? You should never have to execute npm install manually (regardless of the issue), so your issue sounds a little surprising and...

@InsOpDe Strange... Is it maybe possible that it's just a slow connection: - The first `wasp start` almost finished installing. - The second `wasp start` picks up where the first...

## The problem Here's what happens with `wasp db migrate-dev`: 1. The user changes the `prisma.schema` file. 2. The user runs `wasp db migrate-dev`. 3. Wasp generates the new Prisma...

I should add this to the epic.