Stanislav Zhuk

Hi @josefglatz, We use `n` to install Node.js in DDEV, and it always comes with a bundled `npm`. You can switch the npm version in use with: ```bash cat >...

I tried to use `auto` detection for this https://docs.ddev.com/en/stable/users/configuration/config/#nodejs_version ```bash cat > .ddev/web-build/Dockerfile.node

It doesn't work the way I expected. It works for me locally, and a few tests pass, but it fails everywhere else.

`TestProjectPortOverride` doesn't fail locally.

> It had to do with killing docker while ddev was running Yes.

> It would be extremely useful with a fresh DDEV + PhpStorm + Xdebug (and Drupal?) video https://www.youtube.com/watch?v=1dr_4gPtFlQ&t=1838s https://ddev.com/blog/watch-ddev-local-from-scratch-with-windows-wsl2/

I tested the `image:` change with our `postgres` database and found that changing the `image:` alone isn't enough. Docker reuses its cache, so it ends up using the same image...

Different names for images can change the way we pull them in: https://github.com/ddev/ddev/blob/28aa456ed76e0a1aa33359ae96401a06e92c5113/pkg/ddevapp/ddevapp.go#L1865-L1886 Which uses: https://github.com/ddev/ddev/blob/28aa456ed76e0a1aa33359ae96401a06e92c5113/pkg/ddevapp/ddevapp.go#L1905-L1926 And the logic for pulls may be changed with: - #7163

I was thinking about new labels to use them for all Docker resources created by DDEV. `com.ddev.version` seems ideal, clear indicator which includes the version for reliable cleanup. It also...

Rebased to include the latest changes. Not sure it's necessary since we have other PRs to bump chromium, but I did it anyway.