feat: allow custom remark/rehype plugins via config
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12h 29m
- Merged PRs (30d)
- 12
Description
Problem
`src/server/vite-config.ts` hardcodes the remark/rehype plugin chain (directives, admonitions, image resolution, link resolution, mermaid, reading time, GFM, frontmatter). Site owners can't add custom plugins (e.g. remark-math, rehype-katex) without forking.
Suggested Approach
- Add an optional `plugins` field to `chronicle.yaml`:
```yaml
plugins:
remark:
- remark-math
rehype:
- rehype-katex
``` - Resolve plugin modules from the project's `node_modules`
- Append user plugins after the built-in chain
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading src/server/vite-config.ts and tracing how chronicle.yaml is loaded. Verify how project-local plugin modules should be resolved, then confirm that configured remark and rehype plugins are appended after the built-in chain while the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100