sneak/AutistMask
1
0
Fork 0
Code Issues 26 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-08-11 15:24:16 +02:00 by clawbot · 2 comments
clawbot commented 2026-08-11 15:24:16 +02:00
Collaborator
Copy Link
Copy Source

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.
clawbot commented 2026-10-06 02:22:59 +02:00
Author
Collaborator
Copy Link
Copy Source

The module.register() call is in @tailwindcss/node 4.2.1, which the Tailwind CLI loads during the build. #473 pins Tailwind 4.3.1, which calls module.registerHooks() instead. When this issue was filed, script/test-e2e ran the build on the host's Node. It now builds inside the e2e image on Node 22, where module.register() is not runtime-deprecated (that starts in Node 26.0.0), so the e2e output had stopped showing the warning even before this pin.

Model: opus-5-5

The `module.register()` call is in `@tailwindcss/node` 4.2.1, which the Tailwind CLI loads during the build. https://git.eeqj.de/sneak/AutistMask/pulls/473 pins Tailwind 4.3.1, which calls `module.registerHooks()` instead. When this issue was filed, `script/test-e2e` ran the build on the host's Node. It now builds inside the e2e image on Node 22, where `module.register()` is not runtime-deprecated (that starts in Node 26.0.0), so the e2e output had stopped showing the warning even before this pin. Model: opus-5-5
clawbot commented 2026-10-06 05:26:33 +02:00
Author
Collaborator
Copy Link
Copy Source

Resolved by #473, now on next: Tailwind 4.3.1 no longer calls module.register(), the source of this warning, so neither make build nor script/test-e2e can print it.

Model: opus-5-5

Resolved by https://git.eeqj.de/sneak/AutistMask/pulls/473, now on `next`: Tailwind 4.3.1 no longer calls `module.register()`, the source of this warning, so neither `make build` nor `script/test-e2e` can print it. Model: opus-5-5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
critical
Extremely important: data loss, a security hole, production down, or basic use impossible
 merge-ready
needs-checks
needs-rebase
needs-review
needs-rework
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/AutistMask#237