Skip to main content

TypeScript First Verification

TypeScript needs two first gates: a real Node SQL round trip and a browser bundle check. Passing one does not prove the other.

1. Type and package checks​

Start from the generated console directory used in TypeScript Quick Start. After the first npm install has created a lock file:

npm ci
npm run build

The current console has no generated test script. Add application-level tests using your selected test runner before claiming they passed. Use model-aware Assist and compiler diagnostics to verify the request contract; do not grep the generated library to discover methods. Both comment and purpose must be non-empty before execution, and execution uses trusted context.

2. SQLite round trip​

Run the shared School SQLite example from a checkout of teaql-io-site:

npm run verify:school -- --language typescript

The complete TypeScript application uses the same School model as the other six runtimes. The runner generates and builds the workspace, checks root/constant bootstrap twice, saves a school with an audit reason, then starts a new process to read it back. An independent SQLite checker verifies persisted fields and relationships after every phase. Logs, exit codes and row snapshots are retained under artifacts/school/.

3. Browser-safe client​

Bundle a tiny browser entry that imports only the federal client profile. Inspect the bundle/dependency graph and fail if pg, mysql2, better-sqlite3, Node built-ins, or server credentials appear. A root import that accidentally drags SQL drivers into the browser is a release blocker.

4. Governance failures​

Test missing comment/purpose/context/audit, stale version, unknown fields/operators, invalid ranges/paging/sorts, and client attempts to set tenant, merchant, actor, permissions, request policy or purpose policy. All must reject explicitly.

5. SQL and federation evidence​

For Node SQL, retain masked traces proving bound parameters, stable order, native aggregates and exact per-parent Top-N across at least two parents. Inspect the selected provider plan; SQLite can use bounded probes instead of window SQL. For federation, send the generated protocol request to a real TeaQL backend and compare its native/canonical response with a direct backend query. A generic fetch wrapper is not protocol evidence.

6. Regeneration​

Add a field, regenerate the entire package, rebuild both profiles and rerun tests. Record Node/npm/runtime/generator/provider versions, model and lock hashes, commands, exit codes, native responses, and masked trace shapes.