Compiling with `@vercel/ncc` does not copy the `schema.prisma` file.

Bug description

Compiling with vercel/ncc does not copy the schema.prisma` file

How to reproduce

1. Create a using Prisma project
2. install prisma and @prisma/client
3. install vercel/ncc
4. run npx ncc build test.ts -o dist
5. copy dist to Other locations other than the project

Expected behavior

No response

Prisma information

prisma                  : 3.11.0
@prisma/client          : 3.11.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine b371888aaf8f51357c7457d836b86d12da91658b (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli b371888aaf8f51357c7457d836b86d12da91658b (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core b371888aaf8f51357c7457d836b86d12da91658b (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt b371888aaf8f51357c7457d836b86d12da91658b (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : b371888aaf8f51357c7457d836b86d12da91658b
Studio                  : 0.458.0

Environment & setup

• OS:
• Database:
• Node.js version:

Prisma Version

3.11.0

[medz]

@janpio I further tested it, and the newly created pure ts or js project does not have this problem, but using the NestJS framework does not copy schema.prisma to the output directory! Maybe it’s not a Prisma problem, I need to investigate further.

[Jolg42]

Note: @vercel/ncc is used in next.js repo https://github.com/search?q=repo%3Avercel%2Fnext.js+vercel%2Fncc&type=code