Repository navigation
crc32-stream fails on Node.js 26 #1172
Description
Situation
Running citgm crc32-stream passes on Node.js 22 & 24, and fails on Node.js 26
ReferenceError: require is not defined in ES module scope, you can use import instead| Item | Status |
|---|---|
| npm package | https://www.npmjs.com/package/crc32-stream |
| npm status | not deprecated |
| last published | 7.0.1 Oct 14, 2024 |
| weekly downloads | 56,157,816 |
| repo location | https://github.com/archiverjs/node-crc32-stream |
| repo last update to default branch | Oct 14, 2024 |
| repo status | quiet |
| repo CI status | runs in Node.js 18 & 20 |
| lookup - skip | - |
| lookup maintainer 1 | ctalkington |
Repo CI https://github.com/archiverjs/node-crc32-stream/blob/master/.github/workflows/nodejs.yml runs only in EOL Node.js versions 18 & 20.
Cloning the repo and running local tests using Ubuntu 26.04.1 LTS and running under Node.js 22, 24 & 26 confirm the compatibility issues for Node.js 26.
Steps to reproduce
Run https://github.com/nodejs/citgm/actions/workflows/test-module.yml
Module to test: crc32-stream
CITGM repository to checkout: nodejs/citgm
CITGM GitHub ref to checkout: main
Result
Fails in Node.js 26:
| Node.js | npm | macos | ubuntu | windows |
|---|---|---|---|---|
| 22.23.3 | 10.9.9 | PASS | PASS | PASS |
| 24.21.0 | 11.19.0 | PASS | PASS | PASS |
| 26.10.0 | 11.19.1 | FAIL | FAIL | FAIL |
References
Lines 116 to 119 in 4d3d256
cc: @ctalkington
Activity
MikeMcC399 commentedon Oct 5, 2026
Suggestion
Consider upgrading https://github.com/archiverjs/node-crc32-stream to minimum
mocha@11and cutting a new release.If that is not possible, then citgm should skip Node.js 26 for
crc32-stream.MikeMcC399 commentedon Oct 16, 2026
There hasn't been any response, and the last release was 2 years ago.
BethGriggs commentedon Oct 22, 2026
While the other history may suggest the maintainer is unresponsive, ~11 days is too short a timeframe to come to that conclusion. Most modules are volunteer-led, and for someone working full-time, that gives them very limited time to investigate and address the issue. My understanding is this wasn't a user-facing breakage, but a test failure, so the maintainer may only just have become aware of it and not have needed to make a release in that time.
MikeMcC399 commentedon Oct 22, 2026
The assessment was also based on the fact that there are Renovate PRs queued up in https://github.com/archiverjs/node-crc32-stream/pulls?q=is%3Apr+state%3Aopen+author%3Aapp%2Frenovate since Oct 2024.
Thank you for merging #1211 which skips the failing tests. If the maintainer does become active again and merges the
mochaupdate followed by a new release, then we can remove the skip.