DavidWells / DavidWells/markdown-magic
Question: What are the recent changes inside the markdown-magic repo?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 868
- Forks
- 223
- PR merge metrics
- No merged PRs in 30d
Description
Question from @DavidWells (via dictated instruction): "Can you tell me about the recent changes inside of the markdown magic repo?"
Here's a summary of the recent activity, gathered from the package changelogs and repo state as of 2026-07-04. markdown-magic is now a pnpm + Lerna monorepo (independent versioning) with the code split into focused packages under packages/.
Core — markdown-magic (packages/core) → v4.11.0
Went from 4.9.0 → 4.11.0 over May–June 2026:
- 4.11.0 (2026-06-29): cache remote GitHub fetches — avoids re-fetching the same remote content on every run.
- 4.10.x (June 2026):
- Section extraction options for the markdown transform.
- Pass
normalizeBlankLinesoption through to block-transformer. - Pass
forceRemoveCommentsoption through to block-transformer. - Support single-comment mode (
close: false) — blocks that don't need a closing comment.
- 4.9.0 (2026-05-30): added the
dx-argsparser package into the stack.
Block-processing pipeline packages
The parsing/replacing engine is broken into several packages, all actively updated in June 2026:
comment-block-parser(packages/block-parser) → v1.6.4- Single comment mode (
close: false). - Auto-detect syntax from file extension + new
parseTypeflag. - New
firstArgIsTypeoption. - Pattern mode / RegExp support for open & close tags.
- CLI now reads file paths and accepts match-word as the first positional arg.
- Perf: fast-path
dedentString, guard empty option parse.
- Single comment mode (
comment-block-transformer(packages/block-transformer) → v0.8.5- New
normalizeBlankLinesoption/utility andforceRemoveCommentsoption. - Bug fix: correct offset when blocks process out of order.
- Pattern mode enabled for custom open tags.
- New
comment-block-replacer(packages/block-replacer) → v0.1.24- Fix: use correct pattern keys for
removeComments; preloaded-content behavior test updates.
- Fix: use correct pattern keys for
@davidwells/dx-args(packages/dx-args) → v0.2.2 — new argument-parser package (introduced 2026-05-30).comment-block-migrator(packages/block-migrator) → v1.0.2 — package for migrating old → new comment-block syntax (latest bump 2025-11-12).
New plugin packages
Plugins were moved into the packages/ directory structure and split out as standalone packages:
plugin-github-contributors— new GitHub contributors plugin (with TypeScript + release scripts).plugin-dependency-tableplugin-last-modifiedplugin-wordcount
Tooling / infrastructure
- Monorepo managed with pnpm@10 workspaces + Lerna 9 (independent versioning, conventional commits).
- CI/release workflows in
.github/workflows/:test.yml,monorepo.yml,build-binary.yml,release-binary-md-magic.yml,release-binary-block-parser.yml,post-publish.yml,parse-issue.yml, plus Claude integration workflows. - Expanded docs:
docs/(getting-started, syntax-reference, plugin-development, advanced-usage, troubleshooting),CONTRIBUTING.md,AGENTS.md, andexamples/.
Notes on methodology
This clone contains a single squashed commit (a26696a — the Claude integration workflow install), so this summary is derived from the per-package CHANGELOG.md files rather than git log. For the authoritative commit-by-commit history, see the compare views on GitHub.
This issue was generated by the Claude dispatch workflow in response to a repo question.
Contributor guide
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 with the per-package CHANGELOG.md files under packages/ and review the listed .github/workflows/ files for recent repository activity. Use the GitHub compare views for authoritative commit history, then produce a concise, source-backed summary of the changes and note the limitations of the squashed clone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100