agents-js-ts-runtime

Standardize JavaScript and TypeScript tooling by enforcing Bun as the package manager for dependency installation and script execution, while maintaining Node.js as the default runtime for SSR and CI compatibility.

You should avoid Bun as the runtime for SSR applications to ensure Node-specific APIs remain compatible. The policy requires Node.js as the explicit default runtime for SSR, restricting Bun to package management and task running.

The canonical lockfile policy requires using bun.lockb as the sole lockfile. It prohibits mixing bun.lockb with npm, pnpm, or yarn lockfiles to maintain CI-safe command execution and consistent dependency resolution.

Write runtime-agnostic npm scripts by avoiding embedded Bun commands directly within the scripts. Use standard script commands and execute them via bun run, ensuring scripts remain executable across different Node and Bun environments.

Yes, this tooling governance supports React, Solid, and Vue stacks. It applies standardized runtime policies across these front-end frameworks, integrating with Vite, Vitest, Jest, ESLint, and Prettier to maintain CI-safe workflows.

The best way to pin Node.js versions is by using Volta, .node-version, .nvmrc, or the engines field in package.json. This ensures consistent Node runtime environments across development and CI while Bun manages dependencies.