kysely
joist-orm
kysely | joist-orm | |
---|---|---|
42 | 12 | |
4,444 | 234 | |
- | 2.1% | |
9.5 | 9.7 | |
about 1 year ago | 1 day ago | |
TypeScript | TypeScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kysely
-
I made a Twitter clone using Deno and Fresh
Did you check https://github.com/koskimas/kysely ? It was great when I used it. It has great TS support.
- Full-Stack TypeScript with tRPC and React
- Kysely
-
Type-safe S3 Select queries with Kysely
That’s where Kysely comes to the rescue: Kysely is a type-safe and devX-friendly typescript SQL query builder. It was designed to work with PostgreSQL and MySQL, but it exposes a few classes that can let us write queries without being connected to an actual relational database.
- Vue and trpc?
-
Announcing a new TypeScript ORM
prisma (mentioned in the article), zapatos, pgtyped and kysely are the most popular currently I think.
switch between a limited interface and a query builder (MikroORM, TypeORM). This feels like using two different libraries, switching between two different sets of limitations. Kysely is a nice query builder with good TS support, but MikroORM is using Knex instead so you're losing TS, and TypeORM has a custom query builder, less user-friendly than Knex.
-
Which ORM do you prefer with nodejs/Typescript project and why ?
I'd love to see Kysely as an option.
-
You might not need an ORM
Kysely[1] and zapatos[2] are excellent solutions for type-safe typescript query builders. It’s hard to go back to the days of spending 20-30% of your time in the object mapping layer.
[1] https://github.com/koskimas/kysely
-
Simple CQRS in NodeJS with Typescript
Querying the database (PostgreSQL) should not be ground breaking. Personally I like to have full type-safety so we can easily catch bugs during the development time without introducing any tests that are just testing the data type from our datastore to match the data type our API expects. I like to go database schema first, which means that we generate types from the database schema and work with those. Any change to the schema of the database is made with SQL migrations and after that, the typescript types are regenerated. Another approach is to use a code-first tool like TypeORM or Prisma. However in my experience such tools often produce not efficient SQL queries and are less easy to extend. In my projects I use library kysely (https://github.com/koskimas/kysely) with kysely-codegen (https://github.com/RobinBlomberg/kysely-codegen) to have a full type-safe SQL builder.
joist-orm
-
Which ORM would you pick, Prisma or Typeorm
As few comments have already offered alternatives, so I'll mention Joist.
-
Does Typeorm violate the type contract when using relations that aren't explicitly loaded?
I used TypeORM in the past; I had a ton of problems with it. I highly recommend https://joist-orm.io/ instead.
-
What is your favorite way to maintain types and schema in a full stack web app, end-to-end?
Codegen our backend models directly from the db (here a strict 1-1 mapping is a feature imo; we use https://github.com/stephenh/joist-ts/), so we get `Green` added to the backend `Color.ts` for free.
- Joist: An idiomatic ORM library for TypeScript
-
Complex business logic in Node
If you like Rails/ActiveRecord, Joist is our attempt at a "AR-or-better productivity" ORM for TypeScript.
-
Well, shit. Objection.js has been sunset, which ORM/querybuilder did you move to?
Ha, well, as you noted, I'm wary of even bothering to comment :-), but would be great if you checked out Joist: https://joist-orm.io/
-
Looking for a type safe ORM/mapper
Checkout https://github.com/stephenh/joist-ts built from the ground up to be typesafe.
- Ask HN: Who is hiring? (November 2021)
- I used Typeorm in one of our projects and I have nothing but regrets
- What do you think about ORMs?
What are some alternatives?
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
pg-mem - An in memory postgres DB instance for your unit tests
pgtyped - pgTyped - Typesafe SQL in TypeScript
beam - 🪵 Beam Design System
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
graphql-typescript-factories - TypeScript test builders/factories for GraphQL schemas
Sequelize - Feature-rich ORM for modern Node.js and TypeScript, it supports PostgreSQL (with JSON and JSONB support), MySQL, MariaDB, SQLite, MS SQL Server, Snowflake, Oracle DB (v6), DB2 and DB2 for IBM i.
studio - 🎙️ The easiest way to explore and manipulate your data in all of your Prisma projects.
typetta - Node.js ORM written in TypeScript for type lovers.
kysely - A type-safe typescript SQL query builder
express-ts-base - used for my small projects as base
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.