Skip to content

fix(docs): build the docs site again by deduplicating postcss - #182

Open
CJNA wants to merge 1 commit into
chamals3n4:mainfrom
CJNA:fix/docs-duplicate-docusaurus
Open

CJNA wants to merge 1 commit into
chamals3n4:mainfrom
CJNA:fix/docs-duplicate-docusaurus

Conversation

@CJNA

@CJNA CJNA commented Nov 10, 2026

Copy link
Copy Markdown

Purpose

pnpm --filter ./docs build (docusaurus build) fails on main. Every page, the blog and 404 included, fails with "Hook useNavbarMobileSidebar is called outside the " or "Hook useTitleFormatterContext is called outside the ". This makes the docs site build again.

Approach

Cause: the minor-and-patch bump in #172 (#172) moved most of the docs tree to postcss 8.5.32 but left @docusaurus/theme-classic on 8.5.31. pnpm keys a package copy by its peer versions, so it installed two copies of @docusaurus/core, @docusaurus/theme-common and their plugins, one per postcss version. The theme's providers and the swizzled Navbar and Footer (docs/src/theme/) loaded different copies, so React saw two separate contexts.

Fix: every package accepts postcss ^8, so it is now 8.5.32 throughout (pnpm update -r --depth Infinity postcss). Only pnpm-lock.yaml changes, and no package.json. Two version lines change, and 490 lines of duplicate Docusaurus entries go away.

I didn't use a full pnpm dedupe: it would also have changed unrelated backend packages such as jose and express-rate-limit.

Side effect: sanitize-html (job-description cleaning) moves from postcss 8.5.31 to 8.5.32, a patch release.

Related issues

Checklist

  • pnpm test passes locally. Backend unit tests (332), frontend tests (793), the backend build and the frontend type-check pass. I didn't run the backend integration tests locally; CI runs them.
  • Schema changes include the generated migration files. (No schema changes.)
  • Documentation is updated if behaviour changed. (No behaviour change; the docs site builds again.)
  • No keys, passwords or tokens are committed.

🤖 Generated with Claude Code

`docusaurus build` failed on every page with "Hook ... is called outside
the <...Provider>". The minor-and-patch bump in chamals3n4#172 moved most of the
docs tree to postcss 8.5.32 but left @docusaurus/theme-classic on 8.5.31.
pnpm then installed two copies of @docusaurus/core, theme-common and
their plugins, one per postcss version. The theme's providers and the
swizzled Navbar and Footer ended up on different copies, so React saw
two separate contexts.

Every package accepts postcss ^8, so postcss is now 8.5.32 throughout
(also for sanitize-html, a patch release). Lockfile only; no
package.json changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026

Copy link
Copy Markdown

@CJNA is attempting to deploy a commit to the chamalsena Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 1

  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 146b9c7c-4fb2-4e91-9615-4bf86c24e735

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@CJNA CJNA mentioned this pull request Nov 10, 2026
4 tasks done

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant