Filip Sodić

I've removed the client hacks. We don't seem to need them anymore: https://github.com/wasp-lang/wasp/pull/1862.

The final consensus was that it makes sense to turn these into methods (or even properties) on the `AuthUser` object. Instead of having to import `getUsername` and call it on...

# 1 What's the problem? The new structure in Wasp 0.12.0 includes significant changes relevant to our build process. This comment explores what happened and how we've solved it. All...

I wouldn't close it until we figure out what's causing those build issues. Since they weren't happening unless we do `dedupe`, they probably are related.

This issue is not react-specific. For example, if one of our inner dependencies (i.e, package.json files inside web-app and server) specifies prisma/client as a dependency, the runtime resolves to the...

We've released Wasp 0.12.0 with some separation of dependencies, but we weren't thorough enough. The issue still stands: figure out what belongs where and remove duplicates and redundancies. Idea: Why...

> @sodic I wonder if this might be connected with our setup of prisma schemas? I don't think so. I believe this happens because we generate the client outside of...

Not yet unfortunately. We talked about this in person, but commenting for future references.

Wasp 0.12.0 shifted the goals for this issue (i.e., we no longer have different files for configuring TS on client and server), but the rest is still relevant.

Wasp 0.12.0 shifted the goals for this issue (i.e., we no longer have different files for configuring TS on client and server), but the rest is still relevant. Related: https://github.com/wasp-lang/wasp/issues/1827