ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Long-running watch sessions ( rollup --watch ) are the scenario: a build that starts well inside the Node heap limit can, after dozens of rebuilds, terminate with a heap allocation failure instead of a clean rebuild. The documented design makes this plausible: watch mode keeps prior build state and plugin contexts alive for incremental rebuilds, and the modu
GlobalSetup Hook Execution Vitest 1.0.0 introduced the globalSetup and globalTeardown hooks to replace the legacy setupFiles/teardownFiles. The documentation states that globalSetup should run once before any tests are executed. However, users have reported that when the --watch flag is enabled, the hook appears to run before each test file, potentially dupl
Goal Determine whether --parallel can be used reliably with --watch in Mocha 10.0.0 when running on Node.js 18+. Constraints Mocha 10.0.0 removes guaranteed test order when --parallel is enabled. Watch mode re‑runs tests on file changes, but its interaction with concurrent test workers is undocumented. Custom reporters may expect sequential output, which cou
With "incremental": true in tsconfig.json, TypeScript writes a .tsbuildinfo file that records the module graph and emit state. In tsc --watch , this lets the compiler skip re-emitting unchanged files, so retries after a failed or partial run do not produce duplicate writes to the output directory. The behavior I want to pin down is the compatibility boundary
rollup
vitest
mocha
typescript