Skip to content

Release 2.1.191 (2026-08-12)

Bug fixes

  • expose NODE_PATH so baked out-of-workspace npm libs resolve (#2784) A [container].build-command global npm install (npm install -g ) bakes a library into /usr/lib/node_modules — outside /workspace, so it survives the runtime bind-mount — but the package is not on Node's default require path: a global install puts executables on PATH, not libraries on the module search path. require.resolve() therefore returns MODULE_NOT_FOUND unless NODE_PATH points at the npm global root.

build_container_args now sets NODE_PATH=/usr/lib/node_modules on the run path whenever the repo declares a [container].build-command, so a baked library resolves via CommonJS require. The flag is gated on the declared build-command, so every repo that declares none has a byte-identical container environment. An explicit host NODE_PATH wins, letting a consumer override the location.

The value rides the container run invocation rather than a commit-time image ENV because nerdctl's commit --change supports only CMD/ENTRYPOINT, not ENV (verified: 'unknown change directive ENV'); the run-path form works identically across docker and nerdctl.

Documentation

  • add TypeScript to supported-languages tables and dev-ts-node image (#2783) Documentation-review sweep for epic #284: reflect the shipped TypeScript language support in vergil-tooling's consumer-facing docs.

  • consuming-repo-setup.md and repo-profile.md: add typescript to the primary_language value lists (matches the config enum in lib/config.py).

  • ci-architecture.md: add the dev-ts-node (Node 22, 24) entry to the dev container image catalog, mirroring the prod-ts-node images built in vergil-containers.

Ref vergil-project/vergil-tooling#2738

CI Evidence: All gates passed — full audit bundle available. Download →