#106971Fix "Fontconfig" error in runTests.sh npm build process
Description
The build process using the node-js image “ghcr.io/typo3/core-testing-nodejs22:1.2” currently reports an error:
Done.Fontconfig error: Cannot load default config file: No such file: (null)
This seems to have no real effect on the created build. It seems to stem from sharp (image processing) used by libvips, and might affect assets created this way (and probably not being sharpened).
Since not every contributor uses a local npm setup, the “official” runTests execution should not have this error.
The easy solution seems to be to use “ghcr.io/typo3/core-testing-nodejs22:1.2” which has a working fontconfig because it provides the X11 /etc/fonts/ directory.
Reproduce:
$> docker run -it --init --rm -v .:/project -w /project -e HOME=/project/.cache ghcr.io/typo3/core-testing-nodejs22:1.2 /bin/sh $> cd Build && npm install && npm run build
vs. the variant without errors:
$> docker run -it --init --rm -v .:/project -w /project -e HOME=/project/.cache ghcr.io/typo3/core-testing-nodejs22-chrome:1.2 /bin/sh $> cd Build && npm install && npm run build