Skip to content

fix(docs): repair the config comment that broke the build - #31

Merged
evereq merged 1 commit into
developfrom
fix/config-parse-error
Aug 31, 2026
Merged

fix(docs): repair the config comment that broke the build#31
evereq merged 1 commit into
developfrom
fix/config-parse-error

Conversation

@evereq

@evereq evereq commented Aug 31, 2026

Copy link
Copy Markdown
Member

The locale change in #28 left the config unparseable and the build failed:

[ERROR] Error: Docusaurus could not load module at path "/app/docusaurus.config.ts"
Cause: ParseError: Unexpected token, expected ","

Cause

My own tooling error, not a Docusaurus one. The comment I wrote contained a backtick-quoted command name. I built that file through a shell, the shell executed what was inside the backticks, and spliced its stdout into the middle of the comment:

// Docusaurus renders a language dropdown for EVERY locale listed here, but the Docker build runs
yarn run v1.22.22
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. and so only emits English.

Only the first line carries //. The info Visit ... line does not, so the parser stops there.

Rewritten without backticks. The locale change itself — locales: ["en"], matching what the single-locale Docker build actually emits — is unchanged and still correct.

Verified before pushing this time

The config now parses: tsc reports only missing-@types/node complaints from an isolated check, and no ParseError. I did not verify that on the original change, which is why a syntax error reached master.

The nginx-default.conf change from the same PR is intact and unaffected.

🤖 Generated with Claude Code

@evereq
evereq merged commit 9fd7663 into develop Aug 31, 2026
2 checks passed
@greptile-apps

greptile-apps Bot commented Aug 31, 2026

Copy link
Copy Markdown

Greptile Summary

This change restores valid TypeScript comment syntax in website/docusaurus.config.ts and clarifies that locale declarations must match the locales emitted by deployment builds. The English documentation build completed successfully after the repair. For comparison, the preceding revision failed while parsing the malformed configuration comment.

Confidence Score: 5/5

Safe to merge: the repaired Docusaurus configuration parses and the English static documentation site builds successfully.

No actionable defects remain. The affected build path was exercised on both revisions: the earlier revision failed during configuration parsing, while the repaired revision completed static-site generation.

Files Needing Attention: No files need further attention; website/docusaurus.config.ts was the only changed file and its affected build path passed.

T-Rex T-Rex Logs

What T-Rex did

  • Compared the parent and repaired revisions of website/docusaurus.config.ts to verify the repair effect.
  • Validated the original defect by running an English Docusaurus build from a temporary HEAD^ checkout and observing a parse error caused by the malformed comment.
  • Attempted an English Docusaurus production build from a temporary checkout of the parent revision; it failed with a configuration ParseError at line 56.
  • After the repair, executed yarn build --locale en in website and confirmed the build completed successfully for the repaired HEAD.
  • Rebuilt the repaired revision with yarn build --locale en; Docusaurus compiled the client and server, generated the static build, and exited with code 0.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "fix(docs): repair the config comment tha..." | Re-trigger Greptile

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