Preview feature feedback: Integrated seeding

Please share your feedback about the integrated seeding functionality that was released in v2.15.0 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don’t hesitate to ask them in the #prisma-migrate channel in the Prisma Slack.

[flybayer]

I really do not like the decision to make this seed.ts file a script with side effects (vs exporting a function that prisma would then run).

This totally breaks the use case of being able to export a function from the seed file that can be manually invoked somewhere else in my code, such as some test scripts, production scripts, etc.

I urge you to consider changing the functionality to instead export a function so the seed file is side-effect free.

import { PrismaClient } from '@prisma/client'

async function main() {
  const prisma = new PrismaClient()
  const u = await prisma.user.findFirst()
  console.log(u)
}

-main()
+export default main

[rajuashok]

Changing my tsconfig.json to have this:

"module": "commonjs",

instead of this:

"module": "esnext",

fixed it.