Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move all Prisma-related operations and packages to the project's top level #1596

Closed
sodic opened this issue Dec 7, 2023 · 1 comment
Closed

Comments

@sodic
Copy link
Contributor

sodic commented Dec 7, 2023

In Wasp's new structure (prototyped in #1584), @prisma/client is either an SDK dependency or a project dependency, possibly both (see #1595 for details).
It therefore makes most sense to make the prisma package a project dependency.

Anticipated tasks:

  • Modify the generator to list prisma as a dependency in the project's package.json file.
  • Decide where to list the @prisma/client dependency.
  • Verify all Prisma operations successfully execute at the project's top level.
  • Verify everything's OK with the types and the IDE support.
@sodic
Copy link
Contributor Author

sodic commented Feb 29, 2024

Closed with #1604

We've had to make some compromises (e.g., where Prisma is executed).

@sodic sodic closed this as completed Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant