fix(client): Fix deno build after keyed-dmmf migration(#19071)

Merged
Merging
integration/deno-keyed-dmmf
into
main
+41%
IMPROVEMENTS
0
REGRESSIONS
0
UNTOUCHED
3
NEW
0
DROPPED
0

Benchmarks

client generation ~50 Models
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::client generation ~50 Models
+2%
6.3 s
6.2 s
typescript compilation ~50 Models
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::typescript compilation ~50 Models
+1%
70.7 ms
69.8 ms
client generation 100 models with relations
packages/client/src/__tests__/benchmarks/lots-of-relations/lots-of-relations.bench.ts::typescript::client generation 100 models with relations
+41%
54.2 s
38.5 s

Commits

Click on a commit to change the comparison range
ci: run client types on free runners (#19015) Co-authored-by: Joël Galeran <Jolg42@users.noreply.github.com>
base
c6995eb
7 months ago by millsp
+41%
fix(client): Fix deno build after keyed-dmmf migration `dmmfToRuntimeDataModel` is not exported from runitme and is not used in generated client, but was imported. This causes an error for `edge-esm` runtime, used by Deno.
fb5f673
7 months ago by SevInf
ResourcesHomePricingDocsBlogGitHub
Copyright © 2023 CodSpeed Technology SAS. All rights reserved.