Phase 3 installation failure

[ultimike]

Preliminary checklist

• I am using the latest stable version of DDEV
• I am using the latest stable version of this add-on

Expected Behavior

Hiya Bob - sorry it took a few weeks for me to check this out, but better late than never!

Anyway, I was attempting to install this and received the following error:

==> Phase 3: JS toolchain dependencies
Preparing JS toolchain install.
WRITE: /Users/michael/sites/ddevdemo/package.json
Created package.json from Drupal core devDependencies; review and customize as needed.
👎  Install Drupal.org GitLab CI template configs and host shims (bash) 
Could not process post-install action (0) ' Install Drupal.org GitLab CI template configs and host shims'.
For more detail, run `ddev add-on get UltraBob/ddev-drupal-code-quality --verbose` 

A couple of additional notes for you:

1. I'm using DDEV 1.24.10 (I lied to the checkbox in order to submit this issue.)
2. The project that I tried this on does not gitignore dependencies (I know, right?)
3. I'm using Drupal core 10.6.2
4. I accepted the recommended settings when prompted.

Running the ddev add-on get command a second time with --verbose yielded a bit more information:

==> Phase 3: JS toolchain dependencies
Preparing JS toolchain install.
👎  Install Drupal.org GitLab CI template configs and host shims (bash) 
+ set -eu -o pipefail
+ bash dcq-install.sh
 
Could not process post-install action (0) ' Install Drupal.org GitLab CI template configs and host shims': unable to run bash action set -x; set -eu -o pipefail
#ddev-description: Install Drupal.org GitLab CI template configs and host shims
bash dcq-install.sh
: exit status 1, output=+ set -eu -o pipefail
+ bash dcq-install.sh

-mike

Actual Behavior

See above.

Steps To Reproduce

No response

Anything else?

No response

[ultimike]

I tried it a second time with a Drupal 10.6. site, same version of DDEV, but with a site that does ignore dependencies and had an error in Phase 2 (but it kept on chugging along regardless):

Expanding .cspell.json with project-specific settings...
Skipping CSpell expansion: prepare-cspell.php failed.
#ddev-generated
#!/usr/bin/env php

Warning: file_get_contents(.cspell.json): Failed to open stream: No such file or directory in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php on line 27

Fatal error: Uncaught RuntimeException: Unable to read .cspell.json in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php:29
Stack trace:
#0 {main}
  thrown in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php on line 29
PHP Warning:  file_get_contents(.cspell.json): Failed to open stream: No such file or directory in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php on line 27
PHP Fatal error:  Uncaught RuntimeException: Unable to read .cspell.json in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php:29
Stack trace:
#0 {main}
  thrown in /var/www/html/.ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php on line 29
Failed to execute command `bash -c "cd /var/www/html && export _WEB_ROOT='web' && php .ddev/drupal-code-quality/tooling/scripts/prepare-cspell.php"`: exit status 255

In Phase 3, there were lots of deprecation warnings, including this one:

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

After installation finished, I tried out both ddev phpcs and ddev phpstan and things appear to work as expected. I'm not a big user of eslint or some of the other tools.

I do like the fact that it uses the same settings as Drupal.org's Gitlab CI stuff.

I really wanted to see if it would allow me to use VSCode's PhpStan extension (via sanderronde.phpstan-vscode) and have the results populate the "Problems" tab. I was pretty happy to see that this type of thing is working for phpcs and cspell, but unfortunately, I didn't see any PhpStan results in the Problems tab (even when cranking the level up to 8.) Is this a known issue?

If all of the tools are able to return data to the VSCode Problems tab, then this would allow me to forego connecting to DDEV projects' web container directly using Remote Explorer...

I also tried adding a new path to the phpstan.neon file for testing (web/core/modules/node), but it didn't seem to get picked up...

I also tried the eslint stuff in VSCode, and - wow! - that is pretty cool that it works and all the issues are in the Problems tab!

-mike

[UltraBob]

@ultimike thanks for the reports, and sorry to have not gotten back to you earlier.

The cspell related installer error is one that I thought I had gotten rid of, but it is not going to make a huge difference. It crawls your project and ignores some files like LICENSE.txt that come with Drupal, to try and only report spelling issues with things you are responsible for. I'll dig into that. On the first install run, I'm not sure what happened with that. I'll need to think some more.

PHPStan should work, I'm pretty sure that is the extension I provide default extension config for. The thing I've noticed with that extension though: it is triggered by file save. And occasionally, if you have it filtered down to only active file, it loses track of what file you are looking at, and you have to switch to another file and back. If it still doesn't work, please have a look at the output tab, filter to PHP Stan, and let me know what it is saying.

[UltraBob]

@ultimike I THINK I've got both issues you ran into fixed. Please let me know if it still fails to install. By the way, the Node dependency errors will persist. We are bringing in what Drupal Core has, or at least what they had a few weeks ago. The update script to repackage in the newest versions on every release is still on my todo list.

[ultimike]

@UltraBob Thanks for updating all of this - I did another test run during DrupalEasy Office Hours and here's what we found:

Command line usage

1. The installation went much more smoothly today - no errors at all, but as you indicated, there were still some deprecation messages.
2. My project that I was using already had drupal/core-dev installed.
3. After installing, I did a ddev restart as the instructions said.
4. I then tested the following:

• ddev phpstan - worked as advertised
• ddev phpcs - worked, although after the output it did report Failed to run phpcs : exit status 2)
• ddev eslint - I don't think this was working, we let it run for about 2 minutes - it didn't provide any output so I Ctrl-c'd it and got a Failed to run eslint : exit status 130
• ddev stylelint - failed with error:

ConfigurationError: Could not find "stylelint-config-standard-scss". Do you need to install the package or use the "configBasedir" option?
    at getModulePath (file:///var/www/html/node_modules/stylelint/lib/utils/getModulePath.mjs:29:9)
    at loadExtendedConfig (file:///var/www/html/node_modules/stylelint/lib/augmentConfig.mjs:225:21)
    at extendConfig (file:///var/www/html/node_modules/stylelint/lib/augmentConfig.mjs:193:25)
    at augmentConfigBasic (file:///var/www/html/node_modules/stylelint/lib/augmentConfig.mjs:58:26)
    at augmentConfigFull (file:///var/www/html/node_modules/stylelint/lib/augmentConfig.mjs:112:30)
    at Object.transform (file:///var/www/html/node_modules/stylelint/lib/getConfigForFile.mjs:61:37)
    at load (/var/www/html/node_modules/cosmiconfig/dist/Explorer.js:20:38)
    at async Explorer.load (/var/www/html/node_modules/cosmiconfig/dist/Explorer.js:23:20)
    at async getConfigForFile (file:///var/www/html/node_modules/stylelint/lib/getConfigForFile.mjs:68:5)
    at async resolveOptionValue (file:///var/www/html/node_modules/stylelint/lib/utils/resolveOptionValue.mjs:27:24)
Failed to run stylelint : exit status 78

• ddev prettier - appeared to run fine, but also reported the following at the end: Failed to run prettier : exit status 1
• ddev cspell - appeared to run fine, but also reported the following at the end: Failed to run cspell : exit status 1
• ddev composer-validate - appeared to run fine, but also reported the following at the end: Failed to run composer-validate : exit status 2
• ddev checks - same issue with eslint.

Visual Studio Code usage

Next, I wanted to see if issues reported by the tools appear in the VSCode "Problems" tab.

I noticed in the README:

During install, you can choose to merge them into .vscode/settings.json and .vscode/extensions.json, back up and overwrite, or skip and handle them manually.

This wasn't my experience - I didn't get a choice, I did see this though:

👍  Install Drupal.org GitLab CI template configs and host shims (bash) 
BACKUP: /Users/michael/sites/psdcjan2026/.vscode/settings.json.bak
MERGE: /Users/michael/sites/psdcjan2026/.vscode/settings.json
WRITE: /Users/michael/sites/psdcjan2026/.vscode/extensions.json

My project did have an existing .vscode/settings.json file that I had manually configured for a few of the extensions that this addon recommends. My settings assume that VSCode is connected directly to the DDEV web container, so paths to executables looked like /var/www/html/vendor/bin/phpstorm. After the addon was installed, these paths did not change - perhaps the MERGE did not work correctly. I think I confirmed this by manually changing the following in my .vscode/settings.json file:

From:

  "phpstan.binPath": "/var/www/html/vendor/bin/phpstan",
  "phpstan.configFile": "/var/www/html/phpstan.neon",

To:

  "phpstan.binPath": "./.ddev/drupal-code-quality/tooling/bin/phpstan",
  "phpstan.configFile": "./phpstan.neon",

After making this change, PHPStan issues appeared in my VSCode Problems tab. I made similar changes for phpcs, phpcbf, and php and those all appeared to work as well.

Next, I tried stylelint with a CSS file in VSCode and that worked as I expected, with issues in the Problems tab. Same thing for eslint with a JS file and cspell with a php file - sweet!

Okay - that's it for now, I think if you can get the eslint command line stuff working and the .vscode/settings.json MERGE issue sorted, that would be fantastic - I'm happy to retest when you do!

-mike

[UltraBob]

@ultimike Thanks for the thorough testing and detailed report — this is really helpful!

Let me go through what you found:

Installation errors / Node deprecation warnings

There's a substantial overhaul of the Node tooling handlers coming that should smooth out the installation experience. The deprecation warnings from npm are coming from Drupal core's own dependency tree, so those will persist until core updates those packages.

ddev phpcs, ddev prettier, ddev cspell, ddev composer-validate — "Failed to run" messages

These tools are actually working correctly. The "Failed to run X : exit status N" messages come from DDEV itself — it reports any non-zero exit code as a failure. Code quality tools intentionally return non-zero when they find issues, so these messages are expected (if confusing) when the tools detect problems in your code. I've tried to make the message at the end of ddev checks explicit about what the errors are to reduce the impact of the failure message at the end, but do not want to mess with the direct output of the direct tooling runs. I should ask @rfay if there is some way around those failed to run messages.

ddev eslint — appears to hang

ESLint buffers all output until it finishes, so with a large project you can wait several minutes with no visible feedback. The root cause is usually large or minified JS files (vendor bundles, *.min.js, etc.) that the eslint-plugin-prettier rule tries to reformat which is extremely CPU-intensive on big files.

I have a project with a rather poorly set up theme that probably takes upwards of half an hour to return anything. That experience isn't good, though it is native to the tooling, but I don't have a good solution in mind. You can see where eslint is spending its time, and either confirm that it is scanning something that doesn't need scanned or that there is a problem in the add-ons setup:

To diagnose, run ddev eslint --debug. The debug output shows which files ESLint is processing with timestamps, so you can see where the time is being spent. To cut through the noise and just see the file list:

ddev eslint --debug 2>&1 | grep "Lint "

Any large bundled/minified files that you don't need checked can be added to your project's .eslintignore file. For example:

**/*.min.js
**/vendor.js
**/bower_components/**

If you find that the issue is not that it is running into a time-consuming file, please let me know what you found, and I'll try to get it fixed up

ddev stylelint — stylelint-config-standard-scss not found

This happens when your .stylelintrc.json extends stylelint-config-standard-scss but that package isn't installed. Automatic SCSS detection and guided setup is coming in a future release. In the meantime, you can fix this manually:

1. Install the package: ddev exec npm install --save-dev stylelint-config-standard-scss
2. In your .stylelintrc.json, replace "stylelint-config-standard" with "stylelint-config-standard-scss" in the extends array.

If your project doesn't use SCSS and you're seeing this error, it's likely that a previous tool or config left a stale reference — you can just make sure your .stylelintrc.json extends "stylelint-config-standard" instead.

VS Code settings merge not updating existing paths

Maybe the README should be updated, but when you accept the defaults, we select merge for the VSCode settings.

You're right that the merge didn't update your existing tool paths. The current merge behavior is conservative — it only adds keys that don't already exist in your settings.json, so your existing /var/www/html/vendor/bin/phpstan paths were preserved instead of being replaced with the shim paths. I'm going to rethink how this merge works, but for now the workaround is what you did: manually update the tool paths to point to the shims (e.g., ./.ddev/drupal-code-quality/tooling/bin/phpstan). Alternatively, you can back up your settings.json, delete it, and re-run the installer to get a clean generated version.

Thanks again for taking the time to test and document all of this. It's really valuable feedback.

I think most of it has a fix on the way, but if you could let me know what your findings are with eslint, that would help.