chore: add best practices to Prisma ORM example (#9794)
1. **Removed `relationMode` from Prisma schema**:
The
[`relationMode`](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/relation-mode)
setting has been removed from the schema. This setting was primarily
required for databases like Planetscale when foreign key constraints
were not enabled. Since most databases (including Planetscale) [now
support foreign
keys](https://planetscale.com/docs/concepts/foreign-key-constraints),
this configuration should no longer be necessary.
2. **Ensure latest Prisma version on installation**:
The starter now ensures that the latest version of Prisma is installed
during setup. This avoids potential compatibility issues and ensures
users have access to the newest features and fixes.
3. **Custom `outputs` directory for Prisma**:
Prisma files are now generated in a custom `outputs` directory. This
change prevents conflicts across different package managers (e.g., npm,
yarn, pnpm) and improves the reliability of the setup.
4. **Added `.env` file setup instructions**:
Clear instructions have been added to guide users in creating `.env`
files for both the database package and the app. This ensures proper
configuration of environment variables, which makes sure the app starts
up properly.
5. **Refined README with step-by-step instructions**:
The README has been updated with detailed, step-by-step instructions to
simplify the setup process. This includes guidance on installing
dependencies, configuring the database, and running the project.
---------
Co-authored-by: Anthony Shew <anthony.shew@vercel.com>