prisma-client-js

Type-safe database client for TypeScript & Node.js (ORM replacement)

Web Development Data & Databases

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

1.5KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Type-safe database client for TypeScript & Node.js (ORM replacement)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2020-06-09 15:03:38 UTC to 2020-11-01 07:50:08 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jun 8	2020-06-08 00:00:00 UTC	2020-06-15 00:00:00 UTC	2	2
Jun 15	2020-06-15 00:00:00 UTC	2020-06-22 00:00:00 UTC	0	0
Jun 22	2020-06-22 00:00:00 UTC	2020-06-29 00:00:00 UTC	0	0
Jun 29	2020-06-29 00:00:00 UTC	2020-07-06 00:00:00 UTC	0	0
Jul 6	2020-07-06 00:00:00 UTC	2020-07-13 00:00:00 UTC	0	0
Jul 13	2020-07-13 00:00:00 UTC	2020-07-20 00:00:00 UTC	0	0
Jul 20	2020-07-20 00:00:00 UTC	2020-07-27 00:00:00 UTC	0	0
Jul 27	2020-07-27 00:00:00 UTC	2020-08-03 00:00:00 UTC	0	0
Aug 3	2020-08-03 00:00:00 UTC	2020-08-10 00:00:00 UTC	0	0
Aug 10	2020-08-10 00:00:00 UTC	2020-08-17 00:00:00 UTC	0	0
Aug 17	2020-08-17 00:00:00 UTC	2020-08-24 00:00:00 UTC	0	0
Aug 24	2020-08-24 00:00:00 UTC	2020-08-31 00:00:00 UTC	0	0
Aug 31	2020-08-31 00:00:00 UTC	2020-09-07 00:00:00 UTC	0	0
Sep 7	2020-09-07 00:00:00 UTC	2020-09-14 00:00:00 UTC	0	0
Sep 14	2020-09-14 00:00:00 UTC	2020-09-21 00:00:00 UTC	0	0
Sep 21	2020-09-21 00:00:00 UTC	2020-09-28 00:00:00 UTC	0	0
Sep 28	2020-09-28 00:00:00 UTC	2020-10-05 00:00:00 UTC	0	0
Oct 5	2020-10-05 00:00:00 UTC	2020-10-12 00:00:00 UTC	0	0
Oct 12	2020-10-12 00:00:00 UTC	2020-10-19 00:00:00 UTC	0	0
Oct 19	2020-10-19 00:00:00 UTC	2020-10-26 00:00:00 UTC	0	0
Oct 26	2020-10-26 00:00:00 UTC	2020-11-02 00:00:00 UTC	1	1

What Hacker News says

3 sources

benatkin·Nov 1, 2020

Default parameters are huge. I'm glad to see this post and hope libraries will adapt. I think pragmatism outweighs the semantic distinction and json serialization concerns. https://github.com/prisma/prisma-client-js/issues/572

In Intent to stop using 'null' in my JS code

jhanschoo·Jun 9, 2020

I found Prisma 2.0 good for prototyping a service serving a GraphQL-compliant API. One of the features not mentioned here is that it supports a rudimentary form of database query batching (see: https://github.com/prisma/prisma-client-js/issues/153 ), and there seems to be interest in improving it. This helps one with solving the nplusone problem to some extent without having to maintain code specifically for DataLoader + some orm / custom query code. Comparatively, code via the Prisma Client API is usually straightforward and succinct.

In Prisma 2.0 – Type-safe and auto-generated database client

hbrundage·Jun 9, 2020

Prisma's architecture seems novel and ... a little strange to me. It works by running a Rust engine as a subprocess and then communicating with the engine from JS land over a non-spec compliant GraphQL API. The engine holds the actual databae connection pool and does all the SQL generation and data marshalling. See https://www.prisma.io/docs/reference/tools-and-interfaces/pr... for more info on this arrangement. It has some weird ramifications though: - when they go to implement a new feature (like recently added JSON column support) they have to implement it on both sides which can cause bugs like this: https://github.com/prisma/prisma/issues/2432 - they're a little limited to the semantics of GraphQL based RPC, which namely excludes any stateful stuff like arbitrary START TRANSACTION; blocks that might or might not commit. See https://g

Read the rest

ithub.com/prisma/prisma-client-js/issues/349 for more info on that - they don't run everywhere JavaScript runs like the browser or Cloudflare Workers (unless there's something fancy that compiles the engine to WASM I'm not aware of) I wonder if their intention is to re-use the engine between different JS processes for caching / sharding or something like that, or to add Prisma clients in other languages. Why create the indirection? I do like Prisma's type safety compared to the pure TypeScript alternatives like TypeORM and MikroORM -- it's really good at typing the results of specific queries and preventing you from accessing stuff that wasn't explicitly loaded. The style of the query language is the cleanest I've seen out of the three as well IMO. Edit: I think node modules can install arbitrary binaries to some serverless JS runtimes, not sure specifically about Cloudflare but I know their dev tool bundles JS using webpack, which would exclude other binaries from node_modules.

In Prisma 2.0 – Type-safe and auto-generated database client