tripit-js: Instructions file for Codex

• Repo: dvcrn/tripit

Workflow

• Always run mise run build after completing each task.

Default to using Bun instead of Node.js.

• Use bun <file> instead of node <file> or ts-node <file>
• Use bun test instead of jest or vitest
• Use bun build <file.html|file.ts|file.css> instead of webpack or esbuild
• Use bun install instead of npm install or yarn install or pnpm install
• Use bun run <script> instead of npm run <script> or yarn run <script> or pnpm run <script>
• Use bunx <package> <command> instead of npx <package> <command>
• Bun automatically loads .env, so don't use dotenv.

APIs

• Bun.serve() supports WebSockets, HTTPS, and routes. Don't use express.
• bun:sqlite for SQLite. Don't use better-sqlite3.
• Bun.redis for Redis. Don't use ioredis.
• Bun.sql for Postgres. Don't use pg or postgres.js.
• WebSocket is built-in. Don't use ws.
• Prefer Bun.file over node:fs's readFile/writeFile for Bun-only code. The published library and CLI are bundled with --target node, so exported/runtime package code must not depend on the Bun global.
• Bun.$ls instead of execa.

TripIt API Payloads

• TripIt validates JSON requests against its XML XSD. Object key order can matter when TripIt converts JSON to XML for xs:sequence types.
• For reservation objects, keep fields in XSD order: base object fields first, then reservation fields such as booking_rate, supplier_conf_num, supplier_name, is_purchased, notes, and total_cost, then object-specific children such as StartDateTime, EndDateTime, Address, or Segment.
• When create or replace calls return 400 JSON did not validate with the xsd, check outgoing key order before assuming the scalar value itself is invalid.

Testing

Use bun test to run tests.

import { test, expect } from "bun:test";

test("hello world", () => {
  expect(1).toBe(1);
});

Frontend

Use HTML imports with Bun.serve(). Don't use vite. HTML imports fully support React, CSS, Tailwind.