itty-router VS relay-starter-kit

Instead of Next and it's bloat, you should try Svelte, a barebones Svelte (not SvelteKit) app feels like a breeze to scaffold and deploy through Netlify or Vercel with nearly 0 configuration. The same can be said about SvelteKit, though you can just get away by using a minimal router like Itty (https://github.com/kwhitley/itty-router) with barebones Svelte (just run npx create-vite, and follow the interactive scaffold process).

To further simplify development, since we are going to make more than 1 endpoint, we'll install itty-router which is an Express like router to automatically parse out the HTTP method, query params, path params, etc. I also prefer to use prettier to format the code so that it looks consistent.

Is there any good input validator I can use with itty-router for Cloudflare Workers? I am looking for something like express-validator.

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.