Skip to content

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 11 Aug 23:41
· 36 commits to main since this release
63c0dc0

Patch Changes

  • 52bc1ad Thanks @kimjbstar! - Bump prettier from 2.5.1 to 3.9.6 (and @types/prettier to match) and migrate the generator's
    internal formatting calls to prettier 3's async-only API (resolveConfig/format no longer have
    .sync variants). No change to generated output. Also runs jest with
    NODE_OPTIONS=--experimental-vm-modules — prettier 3's CJS entry point uses a dynamic import()
    internally, which Jest's default VM sandbox rejects without that flag.

  • a3f573d Thanks @kimjbstar! - Bump @prisma/generator-helper, @prisma/internals, @prisma/client, and prisma from
    5.5.2 to 6.19.3. Deliberately stopping at 6.x rather than 7.x (what dependabot's PR #81
    proposed): Prisma 7 requires Node ^20.19 || ^22.12 || >=24.0 and drops Node 18 entirely,
    while this project still supports and tests against Node 18. Prisma 6.19.3 still supports
    Node >=18.18.

    Verified against real prisma generate runs (postgresql and mongodb fixtures) on both
    Node 18.20.8 and 22.23.1 — the generated output is unchanged.

    Also adds an explicit DMMF.Document type annotation to PrismaConvertor#dmmf's
    getter/setter — Prisma 6 restructured DMMF's types across an internal @prisma/dmmf
    package boundary that TypeScript's declaration emit can no longer name portably without it
    (TS2742), and enables isolatedModules in tsconfig.json to silence a ts-jest warning
    (TS151002) about the node16 module kind introduced in the prior tsconfig modernization.

  • f5d5a3b Thanks @kimjbstar! - Modernize tsconfig.json ahead of TypeScript 6/7: replace the removed baseUrl /
    moduleResolution: "node" / suppressExcessPropertyErrors / suppressImplicitAnyIndexErrors /
    downlevelIteration options with module/moduleResolution: "node16" (the two must now match)
    and an explicit rootDir. Explicitly pin strict: false since TypeScript 6+ defaults it to
    true and this codebase isn't strict-clean yet. No change to generated output.

    Note: actually bumping the typescript dependency to 7.x is still blocked — TypeScript 7 drops
    the JS compiler API that ts-jest/ts-node need, and neither has shipped compatibility yet
    (see kulshekhar/ts-jest#5366). typescript stays on the 5.x line for now.