test: validate ANSI escape codes are not in redirected composer output (#134)

* test: add ANSI escape code validation for redirected composer output

Adds a test to verify that `lando composer` output does not contain
ANSI escape codes when stdout is redirected to a file.

This test is expected to FAIL until the fix is applied (removing
`--ansi` from the composer tooling command).

Ref lando/drupal#157

* fix: remove --ansi flag from composer tooling command

Composer auto-detects TTY and enables color output when appropriate.
The --ansi flag forced ANSI escape codes even when stdout was redirected
to a file or used in command substitution, breaking scripted usage.

Ref lando/drupal#157

* docs: add CHANGELOG entry for --ansi removal

---------

Co-authored-by: Aaron Feledy <aaron@aaronfeledy.com>

Author: AaronFeledy

CHANGELOG.md

@@ -1,6 +1,7 @@
 ## {{ UNRELEASED_VERSION }} - [{{ UNRELEASED_DATE }}]({{ UNRELEASED_LINK }})
 
 * Updated to [@lando/nginx@1.6.0](https://github.com/lando/nginx/releases/tag/v1.6.0)
+* Removed `--ansi` flag from composer tooling command to prevent escape codes in redirected output
 
 ## v1.10.1 - [February 22, 2026](https://github.com/lando/wordpress/releases/tag/v1.10.1)
 

builders/wordpress.js

@@ -88,7 +88,7 @@ const getDatabaseType = options => {
 const toolingDefaults = {
   'composer': {
     service: 'appserver',
-    cmd: 'composer --ansi',
+    cmd: 'composer',
   },
   'db-import <file>': {
     service: ':host',

examples/wordpress-defaults/README.md

@@ -56,6 +56,9 @@ lando mysql -u root -e "show variables;" | grep innodb_lock_wait_timeout | grep
 
 # Should use composer 2 by default
 lando exec appserver -- /bin/sh -c 'NO_COLOR=1 composer -V' | grep "Composer version 2."
+
+# Should not include ANSI escape codes when output is redirected
+lando composer --version > /tmp/composer-output.txt 2>&1 && ! grep -P '\x1b\[' /tmp/composer-output.txt
 ```
 
 ## Destroy tests