Skip to content

[Bug] Loading "uglify.js" tasks... and ERROR >> Error: Cannot find module '_stream_transform' #24636

@Spixmaster

Description

@Spixmaster

What happened?

Running npm install in directory tests/lib/q-1.4.1/ fails.

It says Error: Cannot find module '_stream_transform'. I am using Nodejs v 26.2.0. That module probably was removed.

What should happen?

Successful command run.

How can this be reproduced?

cd tests/lib/q-1.4.1/ || exit 1
npm install

Matomo version

v5.11.1

PHP version

8.5.7

Server operating system

Arch Linux

What browsers are you seeing the problem on?

No response

Computer operating system

Arch Linux

Relevant log output

even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

added 2994 packages, changed 1 package, and audited 3007 packages in 16s

165 packages are looking for funding
  run `npm fund` for details

189 vulnerabilities (11 low, 102 moderate, 55 high, 21 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm warn allow-scripts 6 packages have install scripts not yet covered by allowScripts:
npm warn allow-scripts   @materializecss/materialize@1.2.2 (install: (install scripts present))
npm warn allow-scripts   core-js@2.6.12 (postinstall: node -e "try{require('./postinstall')}catch(e){}")
npm warn allow-scripts   core-js@3.47.0 (postinstall: node -e "try{require('./postinstall')}catch(e){}")
npm warn allow-scripts   deasync@0.1.23 (install: node ./build.js)
npm warn allow-scripts   ejs@2.7.4 (postinstall: node ./postinstall.js)
npm warn allow-scripts   yorkie@2.0.0 (install: node bin/install.js)
npm warn allow-scripts
npm warn allow-scripts Run `npm approve-scripts --allow-scripts-pending` to review, or `npm approve-scripts <pkg>` to allow.

up to date, audited 1 package in 182ms

found 0 vulnerabilities
npm warn deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated puppeteer@8.0.0: < 19.4.0 is no longer supported

added 615 packages, and audited 616 packages in 18s

56 packages are looking for funding
  run `npm fund` for details

55 vulnerabilities (8 low, 16 moderate, 20 high, 11 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm warn allow-scripts 1 package has install scripts not yet covered by allowScripts:
npm warn allow-scripts   puppeteer@8.0.0 (install: node install.js)
npm warn allow-scripts
npm warn allow-scripts Run `npm approve-scripts --allow-scripts-pending` to review, or `npm approve-scripts <pkg>` to allow.
npm warn deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm warn deprecated rimraf@2.2.8: Rimraf versions prior to v4 are no longer supported
npm warn deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm warn deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm warn deprecated mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm warn deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm warn deprecated glob@3.1.21: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated electron@0.2.1: The original electron project has been moved. Visit github.com/logicalparadox/electron for more details.
npm warn deprecated glob@3.2.1: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated glob@3.2.11: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated coffee-script@1.3.3: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm warn deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm warn deprecated jasmine-node@1.11.0: jasmine-node 1.x & 2.x are deprecated, with known vulnerability in jasmine-growl-reporter pre-2.0.0
npm warn deprecated mocha@1.11.0: Mocha v1.x is no longer supported.
npm warn deprecated sinon@1.7.3: 16.1.1
npm warn deprecated buster-core@0.6.4: No longer maintained

> q@1.4.1 prepublish
> grunt

Loading "uglify.js" tasks...ERROR
>> Error: Cannot find module '_stream_transform'
>> Require stack:
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/browserify-zlib/src/index.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/gzip-size/index.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/maxmin/index.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/grunt-contrib-uglify/tasks/uglify.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/grunt/lib/grunt/task.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/grunt/lib/grunt.js
>> - /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1/node_modules/grunt-cli/bin/grunt
Warning: Task "uglify" not found. Use --force to continue.

Aborted due to warnings.
npm error code 3
npm error path /home/matheus/.cache/paru/clone/matomo/src/matomo/tests/lib/q-1.4.1
npm error command failed
npm error command sh -c grunt
npm error A complete log of this run can be found in: /home/matheus/.cache/npm/_logs/2026-06-14T08_17_04_330Z-debug-0.log
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...
Fehler: ‚matomo-5.11.1-1‘ konnte nicht erstellt werden:

Validations

Metadata

Metadata

Assignees

No one assigned

    Labels

    Potential BugSomething that might be a bug, but needs validation and confirmation it can be reproduced.To TriageAn issue awaiting triage by a Matomo core team member

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions