Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
36589
7bc19692 fix(react): correct the app schema's devServerPort deprecation note The marker claimed "the CLI aliases it", which stopped being true when the application schema's `aliases: ["devServerPort"]` was removed — that generator's CLI option has always been `--port`. A reader trusting the note would pass `--devServerPort`, match nothing, and silently get 4200: the failure this PR exists to remove. Drop the clause so all three schemas carry the same marker.
by FrozenPandaz
Failed
36589
Environment issue→
58ed47d2 cleanup(react): render the mf rspack configs from `port` [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36589
Flaky task→
0e100738 cleanup(react): render the mf rspack configs from `port` The MF rspack templates spelled the dev-server port `devServerPort` while every other template used `port`, so getDefaultTemplateVariables had to supply the same value twice under two names, with a comment claiming the two differed. They never did — both were `options.port ?? 4200`, and the SSR templates the comment appealed to set their own port in setup-ssr-for-{host,remote}. Rename the template expression in the ten rspack-module-federation templates and drop the duplicate. This finishes the devServerPort -> port rename the rest of the branch already made. add-rsbuild.ts keeps `devServerPort`: that is an option on @nx/rsbuild's configuration generator, not a template variable.
by FrozenPandaz
Failed
36589
Flaky task→
0e100738 cleanup(react): render the mf rspack configs from `port` The MF rspack templates spelled the dev-server port `devServerPort` while every other template used `port`, so getDefaultTemplateVariables had to supply the same value twice under two names, with a comment claiming the two differed. They never did — both were `options.port ?? 4200`, and the SSR templates the comment appealed to set their own port in setup-ssr-for-{host,remote}. Rename the template expression in the ten rspack-module-federation templates and drop the duplicate. This finishes the devServerPort -> port rename the rest of the branch already made. add-rsbuild.ts keeps `devServerPort`: that is an option on @nx/rsbuild's configuration generator, not a template variable.
by FrozenPandaz
Succeeded
36589
4523f7b5 chore(rspack): drop the convert-webpack snapshot churn The self-healing snapshot update and its revert cancel out, leaving 18 lines of inline-snapshot re-indentation with identical content — `git diff --ignore-all-space` against the base is empty. Restore the file so the branch touches only what it means to change.
by FrozenPandaz
Failed
36589
efdd3a31 fix(rspack): drop the convert-webpack port snapshot again Self-healing added `port: 4200` here when the react generator started writing the port unconditionally. It now writes one only when requested, and this fixture asks for none, so the field is gone again.
by FrozenPandaz
Failed
36589
Flaky task→
efdd3a31 fix(rspack): drop the convert-webpack port snapshot again Self-healing added `port: 4200` here when the react generator started writing the port unconditionally. It now writes one only when requested, and this fixture asks for none, so the field is gone again.
by FrozenPandaz
Failed
36589
Fix applied→
c02f92f3 fix(react): write the dev-server port onto the generated serve target normalizeOptions always resolves a devServerPort — from --devServerPort, --port, or findFreePort — but createServeTarget never wrote it, so every app generated with the executor targets fell back to the executor's own 4200 default. findFreePort picks the next port by reading serve.options.port off the existing projects, so with nothing ever recorded it returned 4200 every time: a second app in the same workspace silently collided with the first, and an explicit --devServerPort only reached the e2e project's baseUrl, never the server it points at. Write the resolved port on both the webpack and rspack serve targets. A single-app workspace is unchanged (4200 either way).
by FrozenPandaz