knex-types VS postgres-meta

GraphQL.js + Knex.js + knex-types (TypeScript generator for Knex)

And in order to have auto-complete and type checking, you can combine it with knex-types.

I generate TypeScript enums and types from the actual database schema using knex-types as part of the yarn db:reset script that used during local development (after making changes to the db schema migration files). See example project.

I tried to take advantage of TypeORM in a couple of projects, but then reverted back to knex + knex-types — just a PostgreSQL client with query builder works great, IMO, especially for GraphQL API development.

Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).

Luckily, there is a solution! Assuming you have a database table that looks like this (Knex migration):

What grinds my gears it that someone actually started this process with a simple pull request: ADD CRUD permissions. Someone from Supabase said, "sure, no problem, we will work on this next week"... and nope, nothing. Then the PR was randomly closed yesterday! Why? No idea, no explanation. Granted, this was a simple PR and they could be rethinking an easier way to do this. But I digress.

I picked the first issue, which was a bug in the Supabase dashboard, where users could not edit a database column from a primary type to its array type. The dashboard was built with Nextjs and TailwindCSS, using the Supabase-UI components libraries. It looked like was a quick fix to me. After investigation, the error was not with the dashboard but it was an error of insufficient type handling of column type identifiers within the Posgres-Meta package, which was also written by Supabase Team. Then, I headed to the package upstream and fixed it. The PR got merged and released soon after.