BlogDocs

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

Merged
Merging
integration/deno-keyed-dmmf
into
main
+35%
IMPROVEMENTS
1
REGRESSIONS
0
UNTOUCHED
2
NEW
0
DROPPED
0
IGNORED
0

Benchmarks

client generation ~50 Models
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::client generation ~50 Models
+2%
1.2 s
1.2 s
typescript compilation ~50 Models
packages/client/src/__tests__/benchmarks/huge-schema/huge-schema.bench.ts::typescript::typescript compilation ~50 Models
+1%
15 ms
14.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
+35%
10.4 s
7.7 s

Commits

Click on a commit to change the comparison range
base
main
c6995eb
+35%
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
a year ago by SevInf
ResourcesHomePricingDocsBlogGitHub
Copyright © 2024 CodSpeed Technology SAS. All rights reserved.