Prisma 6.18.0 — Release Notes & Engineering Impact

Today, we are excited to share the `6.18.0` stable release 🎉 **🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!** # Prisma ORM Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements: - `prisma init` now creates a `prisma.config.ts` automatically When creating a new project with 6.18.0, `prisma init` will now create a `prisma.config.ts` file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the `schema.prisma` file are now able to be set in the `prisma.config.ts`, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement. - Support for defining your `datasource` in `prisma.config.ts` If you’re adopting the new `prisma.config.ts` setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your `schema.prisma` will be ignored. To set the datasource, we also must include the new `engine` key which we can set to `"classic"` , which will be required for Prisma v7 ```tsx import { defineConfig, env } from "prisma/config"; export default defineConfig({ // The Rust-compiled schema engine engine: "classic", datasource: { url: env('DATABASE_URL'), } }); ``` - https://github.com/prisma/prisma/pull/28291 Support multiple Prisma instances with different providers - https://github.com/prisma/prisma/pull/28305 Add `env` helper function - https://github.com/prisma/prisma/pull/28266 Add support for `js` or `classic` as engine types in `prisma.config` - https://github.com/prisma/prisma/pull/28139 Map `Bytes` to `Uint8Array` depending on Typescript version ### Preparing for Prisma v7 While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to `prisma.config.ts` will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project. # [Prisma Postgres](https://www.prisma.io/postgres) [Prisma Postgres](https://www.prisma.io/postgres) is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements: ### Database Metric in Console Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow: - Total egress - Average response size - Average query duration In addition, you can also get insights into how to improve your query caching and gain better performance. ## Open roles at Prisma Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you. ## Enterprise support Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance. With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.