Personal frontend tooling conventions — Yarn Berry, Biome, node:test, TypeScript with native type-stripping. Use when working on JS/TS projects, configuring tooling, writing tests, or running linters/formatters.
nodeLinker: node-modules — no PnPpackageManager field in package.json pins the versionyarn, not npm/pnpm, unless strictly necessaryyarn npm audit, yarn npm info for registry queries; yarn dlx not npxbiome format alone misses sort/organise actionsbiome check --enforce-assist=truebiome check --fix --enforce-assist=true--enforce-assist=true enforces key/import sorting as errors during lint and applies them during format--fix implies --write; do not pass bothenum, no legacy decorators, no namespace-value merging; erasableSyntaxOnly: true in tsconfig.ts extensions; allowImportingTsExtensions: true for non-bundled workspacesverbatimModuleSyntax: truenode:test for fast unit tests — preferred starting point for all non-UI code.ts tests directly — no tsx, ts-node, or esbuild needed--experimental-strip-types is not needednode --test with a glob, e.g. node --test src/**/*.test.ts{}) for if/else/for/while — no braceless one-liners. Adding or removing statements in braceless blocks requires restructuring; braces keep diffs minimal and refactoring fast.