Codsen Monorepo (Open-Source part)

From-to

• npm only to jsr and cargo
• TS-only code to mix of deno and rust (depending which one suits most)
• eslint to deno lint
• prettier to deno fmt
• uvu to deno test
• c8 to deno coverage
• esbuild to publishing raw TS
• rollup-plugin-dts to deno types
• CLIs in JS to compiled, rust-based CLIs
• lerna/turborepo to mix of nothing and scripts
• benchmark to deno bench

Rules

1. Minimalism and simplicity, 80/20
2. Perf as number one KPI, even at cost of #1. For example, architect the infra to keep alternative versions of the same program and publish the perf winner.
3. Avoid/limit external deps by all means possible, to limit maintenance and liability
4. Two git repos: open source and closed - together housing everything (websites, services, packages etc)
5. Level up on infosec - provenance, socket.dev, snyk
6. Telemetry of all sorts and bean-counting as first-class citizens