fix(calm-suite): declare @docusaurus/faster as dependency in calmguard-docs#2673
Merged
rocketstack-matt merged 1 commit intoJun 17, 2026
Merged
Conversation
…d-docs The Docusaurus build for calmguard-docs fails with `Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@docusaurus/faster' imported from .../node_modules/@docusaurus/bundler/lib/importFaster.js`. Root cause: @docusaurus/core 3.10's `@docusaurus/bundler` imports `@docusaurus/faster` to honour the `future.experimental_faster` / `future.v4` Faster bundler path. `calm-suite/calm-guard/docs/docusaurus.config.ts` sets `future.v4: true`, which exercises the importFaster code path, but the package is not declared in `calm-suite/calm-guard/docs/package.json`. Fix: - Add `@docusaurus/faster: ^3.10.1` to `calm-suite/calm-guard/docs/package.json` (pinned to match the existing @docusaurus/core / @docusaurus/preset-classic). - Regenerate root lockfile via incremental `npm install --package-lock-only` — adds @docusaurus/faster + its 4 new transitive deps (@swc/html, swc-loader, @rspack/core, nested @docusaurus/types/commander) without touching any other workspace's resolutions. All 19 rollup platform-specific binaries preserved. Verified locally: - `npm ci` exits 0 - `npm run build --workspace calmguard-docs` exits 0 (was: `code 1`) Surfaced while preparing PR finos#2664 (A2 of Track A finos#2649) — the regression reproduces identically on plain `origin/main` with no local changes, so it is pre-existing on `main`, not caused by either Track A PR. Fixing it here in a small standalone PR keeps the Track A queue clean. Signed-off-by: Gourav Shah <gjs@opsflow.sh>
rocketstack-matt
approved these changes
Jun 17, 2026
YoofiTT96
pushed a commit
to YoofiTT96/architecture-as-code
that referenced
this pull request
Jun 17, 2026
…d-docs (finos#2673) The Docusaurus build for calmguard-docs fails with `Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@docusaurus/faster' imported from .../node_modules/@docusaurus/bundler/lib/importFaster.js`. Root cause: @docusaurus/core 3.10's `@docusaurus/bundler` imports `@docusaurus/faster` to honour the `future.experimental_faster` / `future.v4` Faster bundler path. `calm-suite/calm-guard/docs/docusaurus.config.ts` sets `future.v4: true`, which exercises the importFaster code path, but the package is not declared in `calm-suite/calm-guard/docs/package.json`. Fix: - Add `@docusaurus/faster: ^3.10.1` to `calm-suite/calm-guard/docs/package.json` (pinned to match the existing @docusaurus/core / @docusaurus/preset-classic). - Regenerate root lockfile via incremental `npm install --package-lock-only` — adds @docusaurus/faster + its 4 new transitive deps (@swc/html, swc-loader, @rspack/core, nested @docusaurus/types/commander) without touching any other workspace's resolutions. All 19 rollup platform-specific binaries preserved. Verified locally: - `npm ci` exits 0 - `npm run build --workspace calmguard-docs` exits 0 (was: `code 1`) Surfaced while preparing PR finos#2664 (A2 of Track A finos#2649) — the regression reproduces identically on plain `origin/main` with no local changes, so it is pre-existing on `main`, not caused by either Track A PR. Fixing it here in a small standalone PR keeps the Track A queue clean. Signed-off-by: Gourav Shah <gjs@opsflow.sh>
gjs-opsflo
added a commit
to gjs-opsflo/architecture-as-code
that referenced
this pull request
Jun 18, 2026
Lockfile reflects: - 11 file: -> bare semver "*" workspace deps (calm-core, mcp-server, github-action, vscode-extension, web-component, apps/studio) - calm-suite/calm-studio/packages/calmscript entry removed (directory deleted in A1's first commit) - @docusaurus/faster@3.10.1 retained (added by finos#2673 on main) - minimatch@10.2.5 hoisted to root (matches main; vsce CJS require works) - @codemirror/autocomplete@6.20.3 preserved (svelte-codemirror-editor peer) - All 19 rollup platform-specific optional dependency variants preserved (validate-lockfile guard upheld) Regen method: incremental `npm install --package-lock-only` against the current origin/main lockfile, then a one-line jq script to remove the stale `calm-suite/calm-studio/packages/calmscript` entry. Avoids the known arborist crash on a clean `rm -rf node_modules package-lock.json && npm install` flow. Verified locally: - `npm ci` exits 0 - `cd calm-suite/calm-studio && npx multi-semantic-release --dry-run` exits 0 (8 @calmstudio/* packages discovered) - `npm run package --workspace calm-plugins/vscode` exits 0 (vsce packages 8.5 MB .vsix) Signed-off-by: Gourav Shah <gjs@opsflow.sh>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Docusaurus build for
calmguard-docsfails onmainwith:Repro on plain
origin/main(no local changes):Root cause:
@docusaurus/core@3.10.1's@docusaurus/bundlerimports@docusaurus/fasterto honour thefuture.experimental_faster/future.v4Faster bundler path.calm-suite/calm-guard/docs/docusaurus.config.tssetsfuture.v4: true, which exercises theimportFastercode path, but@docusaurus/fasteris not declared incalm-suite/calm-guard/docs/package.json.Fix
@docusaurus/faster: ^3.10.1tocalm-suite/calm-guard/docs/package.json(pinned to match the existing@docusaurus/core/@docusaurus/preset-classic).npm install @docusaurus/faster@3.10.1 --workspace calmguard-docs --package-lock-only— adds@docusaurus/faster+ 4 new transitive deps (@swc/html,swc-loader,@rspack/core, nested@docusaurus/types/commander) without touching any other workspace's resolutions. All 19 rollup platform-specific binaries preserved (validate-lockfile guard upheld).Verified locally
npm ciexits 0npm run build --workspace calmguard-docsexits 0 (was:code 1onorigin/main)Out of scope / pre-existing
npm run build --workspace calmguard(the Next.js app, not docs) fails onorigin/mainwithError occurred prerendering page "/dashboard". Reproduces identically on plainorigin/mainwith no local changes — pre-existing, unrelated to this fix.Context
Surfaced while preparing PR #2664 (A2 of Track A #2649 / parent epic #2600) — the calmguard-docs failure showed up on every Track A PR's CI. Fixing it here in a small standalone PR keeps the Track A queue clean rather than bundling it into A1/A2/A3.
Type of Change
Affected Components
docs/)calm-suite/calm-guard/docs/) — Docusaurus build depCommit Message Format ✅
Single commit, DCO-signed:
fix(calm-suite): declare @docusaurus/faster as dependency in calmguard-docsTesting
npm testexits 0)npm run build --workspace calmguard-docsexits 0Checklist
Standalone — does not depend on PR #2661 or PR #2664.