fix(docs): repair the config comment that broke the build - #31
Conversation
Greptile SummaryThis change restores valid TypeScript comment syntax in Confidence Score: 5/5Safe 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;
What T-Rex did
Reviews (1): Last reviewed commit: "fix(docs): repair the config comment tha..." | Re-trigger Greptile |
The locale change in #28 left the config unparseable and the build failed:
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:
Only the first line carries
//. Theinfo 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:
tscreports only missing-@types/nodecomplaints from an isolated check, and noParseError. I did not verify that on the original change, which is why a syntax error reached master.The
nginx-default.confchange from the same PR is intact and unaffected.🤖 Generated with Claude Code