Skip to content

1.41.3

Latest
Latest

Choose a tag to compare

View all tags
@kaihaase kaihaase released this 24 Jul 12:02
1.41.3
d9cedba

A bug fix for lt dev test --shard: sharded Playwright runs now honour your project's own playwright.config.ts reporters instead of silently overriding them.

How to update

npm i -g @lenne.tech/cli@1.41.3

Do I need to do anything?

Only if you run lt dev test --shard in a project whose playwright.config.ts wires a reporter as a release gate (for example a "no-skips" reporter that fails the run when a spec was skipped).

  • Before: each shard was forced to use --reporter=line. A CLI --reporter replaces your configured reporter list, so your gate reporter never ran — a skipped spec could pass with exit 0 under --shard.
  • After: no reporter is forced. Your configured reporters run under --shard, and the HTML reporter is isolated per shard so parallel shards no longer overwrite each other's report.

No configuration changes are required — the fix takes effect automatically once you update.

Under the hood

lt dev test --shard no longer injects --reporter; Playwright auto-adds a compact line/dot reporter when none of your configured reporters print to stdout, and each shard gets its own PLAYWRIGHT_HTML_OUTPUT_DIR (with PLAYWRIGHT_HTML_OPEN=never).

Assets 2
Loading