Skip to content

feat(build): enable build-stats and build-content by default for md2md#1976

Merged
martyanovandrey merged 2 commits into
masterfrom
feat/md2md-default-build-artifacts
Jun 3, 2026
Merged

feat(build): enable build-stats and build-content by default for md2md#1976
martyanovandrey merged 2 commits into
masterfrom
feat/md2md-default-build-artifacts

Conversation

@martyanovandrey
Copy link
Copy Markdown
Contributor

Summary

For `--output-format=md` builds, both `--build-stats` and `--build-content` now default to `true` so md2md CI pipelines emit `yfm-build-stats.json` and `yfm-build-content.json` without an explicit opt-in. For `html` builds the flags stay off by default — local dev doesn't pay for an extra fs walk by default, and the content map's main consumers (search reindex, change notifications) read from the md2md output anyway.

Per-feature Config hooks resolve the default at config-resolution time using config.outputFormat, so explicit --no-build-stats / --no-build-content and yfm-config buildStats: false / buildContent: false continue to win over the per-format default.

The flag descriptions in yfm --help are updated accordingly.

A docs PR is opened separately.

For --output-format=md, both --build-stats and --build-content now default
to true so md2md CI pipelines get yfm-build-stats.json and
yfm-build-content.json without an explicit opt-in. For html builds the
flags stay off by default. Users can opt out via --no-build-stats /
--no-build-content (or buildStats: false / buildContent: false in yfm
config), and the explicit values continue to win over the per-format
default.
These artifacts default to on for md2md builds, so every md2md fixture
output would otherwise carry yfm-build-stats.json and yfm-build-content.json
in its filelist snapshot. Treat them like the existing _bundle/ and _search/
system paths.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 3, 2026

@martyanovandrey martyanovandrey merged commit 029b4b5 into master Jun 3, 2026
12 checks passed
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.

2 participants