npm / @flakiness/playwright
@flakiness/playwright
What changed in @flakiness/playwright 1 to 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
7 breaking12 new APIs and options6 behavior and defaults3 tooling12 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@flakiness/playwright 212 changes
Breaking changes 4
The separate balanced-sharding executable is gone; configure shardBalancing and run plain playwright test --shard=N/M instead.
The supported Node.js engine range now starts at 22.9.0; Node 20 has been dropped.
open now defaults to 'never', so the reporter prints the flakiness show command instead of launching a browser; set it to 'on-failure' to restore the old behavior.
Balanced sharding now requires a timings file, produced with flakiness-playwright-timings build or fetch and committed, making shard splits stable across runs.
New APIs and options 2
GitLab CI/CD uploads can authenticate without an access token by declaring an id_tokens entry named FLAKINESS_ID_TOKEN with an aud matching flakinessProject.
Configure balanced sharding as a reporter option and use Playwright's native sharding command.
Behavior and default changes 1
Balanced sharding requires Playwright 1.62+; on older versions the reporter warns and Playwright's native sharding applies.
Tooling 1
Each shard prints timings coverage, predicted per-shard loads, and a balance percentage before the run, then the predicted-vs-actual delta after it.
Fixes and other changes 4
Improves support for serial suites.
Fixes a corner case in the sharding algorithm.
Improves the shard selection heuristic.
Node 20 support was brought back, allowing developers to use the package with Node 20 again.
@flakiness/playwright 128 changes
Breaking changes 3
Playwright project metadata is no longer used to define timelines.
Run titles are no longer auto-detected.
A Flakiness Report is no longer generated when no Playwright project is given.
New APIs and options 10
The flakiness-playwright-shard command supports the --list flag.
Adds a fetch subcommand to the timings binary.
Adds a flag to read test duration hints.
Runs balanced shards using --shard; Playwright test arguments pass through as usual.
Configure the reporter with a Flakiness project so balanced sharding can use its historical durations.
Introduces perfect sharding.
Embeds information about the runtime, test runner, and reporter.
Attachments are attributed to steps, making their association with individual steps available to developers.
Adds a title option to name reports.
Adds support for Github OIDC; see the uploading reports documentation for details.
Behavior and default changes 5
Sharded runs now generate a default title.
The Durations API supports anonymous access.
The sharding algorithm was improved.
Sharding now applies only to leaf projects and tests.
Stdio is represented as a unified array with real-time timestamps.
Tooling 2
Introduces a new binary for working with Playwright test timings.
Uses historical durations from Flakiness.io to generate a Playwright --test-list for each shard, aiming to make CI shards finish closer together.
Fixes and other changes 8
Anonymous Playwright projects are now properly named.
Sharding now respects --fully-parallel.
The telemetry timer no longer retains the host process.
Tests from serial suites are no longer sharded.
Only projects that were actually executed are reported.
PNPM is now properly detected for the show-report message.
Avoids the “dynamic require of tty is not supported” error.
Support initialized repositories that have no commits.