maybe VS relay-starter-kit

Maybe is the story of a comeback. It was shut down in July, 2023. Not wanting to waste the $1,000,000 from investors, Maybe was open-sourced this past January as a fully transparent, open-source, community-backed personal finance app. It was hard to miss because it was trending on GitHub for the entire week.

View on GitHub

And doing so could end up making it accelerate, possibly making the unviable business eventually viable: https://github.com/maybe-finance/maybe

https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)

GitHub

It also helps to have a REPL shell for Knex.js — https://i.imgur.com/P5bVdoC.gif

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.

GraphQL API and Relay Starter Kit— an example of implementing GraphQL API optimized for the serverless environment (Google Cloud Functions) + a reverse proxy using Cloudflare Workers

It helps to have a monorepo setup with packages/projects such as "api", "worker" (cron job) etc. all consuming the same environment variables (db connection settings etc.), when the cron job "serverless" function is deployed, it just picks the required environment variables from the shared "env" folder/package.