Problem
After the Vitest 4 migration in #372/#379, npm test fails before loading tests under Node 18.19.1 because Rolldown imports node:util.styleText, which that runtime does not export. CI already standardizes on Node 22 (.github/workflows/ci.yml:15 and sibling jobs), but package.json has no top-level engines.node declaration and the local-development instructions do not identify the required version.
Reproduction
$ node --version
v18.19.1
$ npm test
SyntaxError: The requested module node:util does not provide an export named styleText
The same suite passes under Node 22.
Suggested scope
Declare the supported Node version in package.json and add a version-manager hint (.nvmrc or the project-standard equivalent), then align the contributor/local-development documentation. Consider whether npm ci should fail clearly on an unsupported runtime.
Deferred from #349 because it is test-toolchain setup, unrelated to deleting the unused Dashboard authoring session.
Problem
After the Vitest 4 migration in #372/#379,
npm testfails before loading tests under Node 18.19.1 because Rolldown importsnode:util.styleText, which that runtime does not export. CI already standardizes on Node 22 (.github/workflows/ci.yml:15and sibling jobs), butpackage.jsonhas no top-levelengines.nodedeclaration and the local-development instructions do not identify the required version.Reproduction
The same suite passes under Node 22.
Suggested scope
Declare the supported Node version in
package.jsonand add a version-manager hint (.nvmrcor the project-standard equivalent), then align the contributor/local-development documentation. Consider whethernpm cishould fail clearly on an unsupported runtime.Deferred from #349 because it is test-toolchain setup, unrelated to deleting the unused Dashboard authoring session.