chore: script/test-e2e emits DEP0205 module.register() deprecation warning #237

New Issue

clawbot · 2026-08-11T15:24:16+02:00

clawbot commented

2026-08-11 15:24:16 +02:00

The build step invoked by script/test-e2e prints:

DEP0205 DeprecationWarning: module.register() is deprecated

Pre-existing on next; noticed while running the e2e suite for #154 and deliberately not chased mid-task.

Captured rather than ignored because a deprecation warning is an action item with a deadline attached — it becomes a hard failure on some future Node release, and the pinned Node version in script/bootstrap will move eventually. Cheaper to resolve now than the first time CI breaks on it.

Implementation requirements

Identify which dependency calls module.register() — it is unlikely to be repo code; check the esbuild/tailwind/jest toolchain first.
If it is a transitive dependency, establish whether a newer version drops the call before considering any workaround.
Do NOT suppress the warning. Silencing a deprecation notice converts a scheduled problem into an unscheduled one.
If it cannot be resolved without an unwanted upgrade, record that conclusion and the Node version at which it becomes fatal, so the deadline is known rather than discovered.

Definition of done

The source of the module.register() call is identified and named.
Either the warning no longer appears, or the reason it cannot yet be removed is documented along with the Node version that will make it fatal.
make test-e2e still passes.
TODO.md updated in the same commit.
make check passes.

The build step invoked by `script/test-e2e` prints: ``` DEP0205 DeprecationWarning: module.register() is deprecated ``` Pre-existing on `next`; noticed while running the e2e suite for https://git.eeqj.de/sneak/AutistMask/issues/154 and deliberately not chased mid-task. Captured rather than ignored because a deprecation warning is an action item with a deadline attached — it becomes a hard failure on some future Node release, and the pinned Node version in `script/bootstrap` will move eventually. Cheaper to resolve now than the first time CI breaks on it. ## Implementation requirements - Identify which dependency calls `module.register()` — it is unlikely to be repo code; check the esbuild/tailwind/jest toolchain first. - If it is a transitive dependency, establish whether a newer version drops the call before considering any workaround. - Do NOT suppress the warning. Silencing a deprecation notice converts a scheduled problem into an unscheduled one. - If it cannot be resolved without an unwanted upgrade, record that conclusion and the Node version at which it becomes fatal, so the deadline is known rather than discovered. ## Definition of done - [ ] The source of the `module.register()` call is identified and named. - [ ] Either the warning no longer appears, or the reason it cannot yet be removed is documented along with the Node version that will make it fatal. - [ ] `make test-e2e` still passes. - [ ] `TODO.md` updated in the same commit. - [ ] `make check` passes.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/AutistMask#237