feat: add Postgres with Drizzle template

[atharvadeosthale]

What does this PR do?

Adds node-typescript/postgres-with-drizzle, a function that serves a todo API on Appwrite Postgres through Drizzle ORM.

Route	Action
GET /	List todos
POST /	Create a todo from { title }
GET /:id	Get a todo
PATCH /:id	Update title or completed
DELETE /:id	Delete a todo

• The schema lives in src/schema.ts, and the generated SQL migrations live in drizzle/.
• The function never changes the schema. Developers apply migrations from their machine with npm run db:migrate and create new ones with npm run db:generate.
• The only setting is DATABASE_URL, the database's connection string.

drizzle-kit pulls in an esbuild version with a moderate advisory through @esbuild-kit/core-utils, which fails npm audit. An npm override moves that copy to ^0.25.12. Migrations still generate the same SQL.

Test Plan

Deployed as a Node 22 function against an Appwrite Postgres database:

• Before migrating, the function created no tables, and requests failed on the missing todos table.
• npm run db:migrate created todos and Drizzle's migrations table. A second run changed nothing.
• Every route returned the expected response after the migration.
• Errors return the documented status and message: an empty or 256-character title, invalid JSON, a non-boolean completed, an empty update, a missing todo, and an unsupported method.
• Invalid IDs return 404 without querying: /0x1, /1e0, /1.0, /0, /-1, /2147483648, /abc and /1/extra.
• The same routes pass through the pooled connection string (port 6432). 2,000 prepared-statement queries from 20 clients spread across all 10 pooler backends with no failures.
• On Node 22: npm ci --ignore-scripts, npm run build, npm audit (0 vulnerabilities) and prettier --check pass. drizzle-kit generate reports no schema drift.

The npm audit job fails on six existing templates that this PR doesn't change: email-contact-form, generate-pdf, password-expiry, payments-with-stripe, subscriptions-with-stripe and sync-with-pinecone.

Related PRs and Issues

None.

Have you read the Contributing Guidelines on issues?

Yes.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds a new template project for a todo API.

The PR appears safe to merge; no new actionable issue or outstanding previous finding remains.

Summary

The template now applies migrations from a developer’s machine rather than on function startup. It also disables prepared statements for pooled connections and validates todo IDs as decimal integers within the database column’s range.

_{Reviews (2) · Last reviewed commit: "fix: disable prepared statements for poo..."}

[atharvadeosthale]

@greptileai review