kysely
garph
kysely | garph | |
---|---|---|
42 | 27 | |
4,444 | 1,287 | |
- | 1.0% | |
9.5 | 7.4 | |
about 1 year ago | 2 months ago | |
TypeScript | TypeScript | |
MIT License | 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.
garph
-
Best backend for GQL?
https://garph.dev is pretty good. I have been using it for two months and love the experience. I had started out with nexus and briefly also evaluted pothos but switched to garph because the dev experience was superior. It takes full advantage of the structural type system of typescript rather than frameworks that lean more towards java style idioms.
-
Ask HN: Who wants to be hired? (December 2023)
Location: EU, Germany
Remote: Yes
Willing to relocate: Yes
Technologies: HTML, CSS, TailwindCSS, JavaScript, TypeScript, Node.js, React/Next.js, Vue/Nuxt, GraphQL, REST, Postgres, Git, AWS, Docker + K8s
GitHub: https://github.com/mishushakov
LinkedIn: https://linkedin.com/in/mishushakov
Email: hey at mish.co
Most recently, I worked at Step CI a Technical Founder and authored the API-Testing Framework (https://stepci.com) and Garph (https://garph.dev), a full-stack API-Framework, which brings the developer-experience of tRPC to GraphQL.
My passion is in making tools developers love using and make them more productive.
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
If you want something like tRPC but for GraphQL, you should definitely give Garph a try: https://garph.dev
-
I reviewed 1,000s of GraphQL vs. REST perspectives
Amazing findings! Really admire your effort here
Btw. If you're building a GraphQL API using TypeScript, you should take a look at garph (https://garph.dev) which helps you to create type-safe GraphQL APIs without code-gen
-
Next.js and GraphQL: The Perfect Combination for Full Stack Development
The next step is undoubtedly the creation of our GraphQL Schema using Garph to create a totally type-safe API without needing to do codegen.
- Garph - Fullstack Open-source GraphQL framework for TypeScript
- Garph - Fullstack Open-Source GraphQL framework for TypeScript
- Garph - Fullstack GraphQL framework for TypeScript
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.
zodios - typescript http client and server with zod validation
pgtyped - pgTyped - Typesafe SQL in TypeScript
sonner - An opinionated toast component for React.
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.
ts-reset - A 'CSS reset' for TypeScript, improving types for common JavaScript API's
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.
nuxt-scheduler - Create scheduled jobs with human readable time settings
typetta - Node.js ORM written in TypeScript for type lovers.
llm-client - LLMClient - JS/TS Use prompt signatures, Agents, Reasoning, Function calling, RAG and more. Based on the Stanford DSP Paper
express-ts-base - used for my small projects as base
suspense - Utilities for working with React Suspense