[Bug] grunt not found #23667
Description
What happened?
I install via npm install --omit dev which fails.
- Installing monolog/monolog (1.27.1): Extracting archive
- Installing symfony/monolog-bridge (v5.4.45): Extracting archive
- Installing symfony/process (v5.4.47): Extracting archive
- Installing szymach/c-pchart (v3.0.17): Extracting archive
- Installing tecnickcom/tcpdf (6.10.0): Extracting archive
- Installing tedivm/jshrink (v1.8.0): Extracting archive
- Installing symfony/polyfill-php81 (v1.33.0): Extracting archive
- Installing twig/twig (v3.11.3): Extracting archive
- Installing wikimedia/less.php (v3.2.1): Extracting archive
Package lox/xhprof is abandoned, you should avoid using it. No replacement was suggested.
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
29 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
> q@1.4.1 prepublish
> grunt
sh: Zeile 1: grunt: Kommando nicht gefunden
npm error code 127
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/2025-10-11T14_17_25_840Z-debug-0.log
==> FEHLER: Ein Fehler geschah in build().
Breche ab...
Fehler: ‚matomo-5.5.0-1‘ konnte nicht erstellt werden:
Fehler: Pakete konnten nicht erstellt werden: matomo-5.5.0-1
corrupted double-linked list
[1] 646011 IOT instruction (core dumped) paru -S matomoWhat should happen?
No error. Probably move grunt-cli from devDependencies to dependencies.
How can this be reproduced?
Clone repository and run npm install --omit dev in it.
Matomo version
5.5.0
PHP version
No response
Server operating system
No response
What browsers are you seeing the problem on?
No response
Computer operating system
No response
Relevant log output
Validations
- Read our Contributing Guidelines.
- Follow our Security Policy.
- Check that there isn't already an issue that reports the same bug to avoid creating duplicates.
- The provided steps to reproduce is a minimal reproducible of the Bug.