Skip to content

Update website dependencies and standalone builds - #1149

Open
cwil2072 wants to merge 1 commit into
TheSpaghettiDetective:masterfrom
cwil2072:agent/website-dependency-maintenance
Open

cwil2072 wants to merge 1 commit into
TheSpaghettiDetective:masterfrom
cwil2072:agent/website-dependency-maintenance

Conversation

@cwil2072

Copy link
Copy Markdown

Summary

  • update all Docusaurus packages from 3.7.0 to 3.8.1
  • migrate @svgr/webpack from 5.5.0 to 8.1.0 and resolve compatible Webpack transitives
  • regenerate the npm and Yarn lockfiles, repairing the malformed Yarn v1 lock
  • point documentation links and assets maintained outside this checkout to canonical obico.io URLs so clean-checkout builds do not require external blog files

This is a clean, tested alternative to #1075. It intentionally stays on Docusaurus 3.8.1: version 3.10.2 was evaluated but caused a repeatable heap OOM during the documented docs dev-server workflow.

Validation

  • npm ci
  • yarn install --frozen-lockfile --non-interactive
  • yarn build for all 9 locales
  • npm audit --omit=dev: 74 advisories to 50
  • full npm audit: 74 advisories to 50
  • npm audit fix --package-lock-only --ignore-scripts --dry-run: no additional safe changes

Known issue

The yarn start command did not become ready within 2m29 and reached approximately 8.6 GB RSS. Untouched master on Docusaurus 3.7 showed the same behavior, reaching approximately 8.4 GB after 2m24, so this appears pre-existing. Docusaurus 3.10.2 showed a worse immediate heap OOM at both 4 GB and 8 GB on Node 24 and also reproduced on Node 22, so it was not retained.

No test or type-check scripts are defined for website.

Machine: thebrain-chris
Agent: codex
Agent-Framework: openai-codex-cli
Agent-Model-Family: gpt-5
@cwil2072
cwil2072 marked this pull request as ready for review July 30, 2026 18:01
@kennethjiang

Copy link
Copy Markdown
Contributor

website is connected to our CMS/blog workflow and isn’t intended for self-hosted users to build. Self-hosted users have no practical reason to build or deploy the marketing site or blog.

Is there a use case I’m missing that requires the static website to build cleanly from the obico-server repository alone?

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.

2 participants