Skip to content

fix(docs): resolve expressive-code build warnings for latte and env#83

Merged
markshust merged 1 commit into
developfrom
feature/docs-build-warnings
May 26, 2026
Merged

fix(docs): resolve expressive-code build warnings for latte and env#83
markshust merged 1 commit into
developfrom
feature/docs-build-warnings

Conversation

@markshust
Copy link
Copy Markdown
Collaborator

Summary

  • Bundle MIT-licensed Latte TextMate grammar from smuuf/vscode-latte-lang so ```latte fenced blocks highlight correctly (LICENSE preserved next to the grammar JSON)
  • Alias `env` codeblocks to Shiki's bundled `dotenv` grammar
  • Apply `npm audit fix` to clear 8 transitive/patch-level vulns (Astro 6.0.1 → 6.1.x patch, plus defu/devalue/h3/picomatch). No breaking changes; `package.json` ranges were untouched, only the lockfile moved.

Why

Every push to `develop` was producing build warnings like `Error while highlighting code block using language "latte" / "env"`. Builds still succeeded (falling back to `txt`), but code samples in the docs rendered without syntax highlighting.

Test plan

  • `cd docs && npm run build` — completes with zero `expressive-code` warnings
  • `npm run dev` — verified locally on:
    • `/docs/packages/view-latte/` (latte highlighting)
    • `/docs/tutorials/build-a-blog/` (latte highlighting)
    • `/docs/packages/database-pgsql/`, `/docs/packages/skeleton/` (env highlighting)
  • `npm audit` reports `found 0 vulnerabilities`

🤖 Generated with Claude Code

Build was emitting warnings on every push to develop because Shiki had no
grammar for ```latte or ```env fenced code blocks.

- Bundle MIT-licensed Latte TextMate grammar from smuuf/vscode-latte-lang
  (normalized name to lowercase so the markdown fence matches)
- Alias `env` codeblocks to Shiki's bundled dotenv grammar
- Apply `npm audit fix` (8 vulns, all transitive/patch-level, no breaking changes)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added bug Something isn't working breaking Introduces a breaking change labels May 26, 2026
@markshust markshust merged commit c5787f8 into develop May 26, 2026
1 check passed
@markshust markshust deleted the feature/docs-build-warnings branch May 26, 2026 16:55
@markshust markshust removed the breaking Introduces a breaking change label May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant