JavaScript/TypeScript Practices

How TypeScript is written in pkg/@eserstack/*: modules, runtime access, types, tests and React UI.

Always

• Always import as a namespace (import * as path from "@std/path"), in code, tests, JSDoc @example blocks and READMEs alike; the only exception is runtime from @eserstack/standards/cross-runtime
• Named exports on the declaration; no default exports except where laroux loads a module's default
• Relative imports carry the .ts extension; a package's entry is mod.ts; no export *
• File system, env and process access goes through runtime, never Deno.* or process.env in library code
• Only booleans use implicit checks; defaults use ??, never ||
• validate-code-conventions (in deno task cli ok) enforces the import and || rules on new code; existing violations sit in .eser/baselines/code-conventions.json, which only ever shrinks
• null for absent values you define; instanceof for object types
• return await in async functions; every promise is awaited or owned
• Tests are co-located *.test.ts, run with deno task cli test
• deno fmt and deno lint enforce formatting and the basics; run them instead of hand-checking

References