Generate `@prisma/client` even when schema is empty?
See original GitHub issueOrigin https://github.com/prisma/prisma2/issues/1592
Is it something we want to do?
If so we’ll need to change generate
errors into warnings and think of a nice DX when using the (empty) generated client in code.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Generating the client (Concepts) - Prisma
This page explains how to generate Prisma Client. It also provides additional context on the generated client, typical workflows and Node.js configuration.
Read more >Prisma SQLServer Connection database was empty
prisma file and you will not be able to generate Prisma Client with the prisma generate command. To fix this, you have two...
Read more >prisma default empty string - You.com | The search engine you control.
This can point to a file that implements a generator or specify a built-in generator directly. ... Default values are currently not allowed...
Read more >Prisma | NestJS - A progressive Node.js framework
Note The prisma generate command reads your Prisma schema and updates the generated Prisma Client library inside node_modules/@prisma/client .
Read more >How To Build a REST API with Prisma and PostgreSQL
Prisma Client : An auto-generated and type-safe query builder. ... Next, navigate into the directory and initialize an empty npm project.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for responding @Jolg42! I’ll try out your suggestion and open up an issue if needed.
Hi @RyanHedges, thanks for the feedback!
You could try setting the following env var to true:
Which will disable the
generate
triggered during thepostinstall
lifecycle and not error anymore.I don’t think it covers what you want to do completely though and would recommend creating a new issue .