Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

core: incremental generation against an existing output (`--incremental`)

Ouverte
  • Quelque chose ne va pas ?
#1,189 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

@avivkeller y travaille déjà.

Depuis le 26/10/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

CLI

Hey folks 👋

Summary

doc-kit generate --incremental would make a build against an existing output only redo what changed in --input since that output was produced. The output itself would record what it was built from, so the next build can tell which pages are stale and leave the rest alone, a bit like ISR does for static pages.

doc-kit generate -i 'doc/api/*.md' -t web -o out/ --incremental

Why

Every build regenerates everything today, even for a one-line change: on the Node.js docs, every target, all 782 pages, the search index and the sitemap. That costs build time on every commit, and it means every file gets rewritten and redeployed, so caches and CDNs can't tell what actually changed.

Proposal

A manifest that travels with the output

Write a small manifest next to the output (e.g. out/.doc-kit/manifest.json) recording:

  • a salt: the doc-kit version and a hash of the resolved configuration, including the changelog, index.md and the type map
  • a content hash for every input file
  • for every output file: which inputs produced it, and its own hash

With --incremental, doc-kit reads that manifest from --output and compares it with the current inputs:

Situation What happens
No manifest, or it can't be read Full build (never a wrong output)
Salt differs (config, version, type map, ...) Full build
Some inputs changed or were added Their pages are rebuilt, plus the outputs that combine every page
An input was deleted Its outputs are removed
Nothing changed Nothing is rewritten

Some outputs fold in every page and have to be rebuilt whenever anything changes: all.html, all.json, sitemap.xml, llms.txt, llms-full.txt and orama-db.json. Headings matter too: if a changed file's headings changed, every page's sidebar changed with them.

Unchanged files should not be rewritten at all, so their modification times stay stable for whatever deploys or caches them.

What reruns no matter what

Aviv's #1010 already found the honest floors here: parsing and metadata extraction are about as fast as reading a cache, so they rerun every time; all.html is rebuilt whenever anything changed; and the client bundle always rebuilds, because building it from a partial set of pages changes its chunk hashes. What incremental builds can save is mostly per-page work: on the Node.js docs, jsx-ast (~3.5s with 4 threads) and rendering (~1.5-2s), out of a ~7-9s web build.

Relation to #1010

#1010 does incremental builds with a separate content-addressed cache (node_modules/.cache/doc-kit), which is great when that folder survives between runs. Anchoring the manifest on the output instead means it also works when all you have is the previous build's output, e.g. a deployed site or a CI artifact, with no extra cache to restore. Both could share the same machinery. #1010 has been idle since August and predates the package reorganisation, so this issue could track picking it back up in either form.

Prerequisites
  • Byte-identical output between builds. Comparing hashes only works if an unchanged input gives the same output every time. Today the output order depends on which worker finishes first (#1183), and orama-db.json changes on every build (#1184).
  • An output abstraction, if the output isn't a folder (see #1188): the manifest has to be read from and written to wherever --output points.

Acceptance criteria

  • A second --incremental build with no changes rewrites nothing and leaves the output byte-identical.
  • Changing one Markdown file rewrites only its pages and the combined outputs.
  • Deleting an input removes its outputs.
  • A config or doc-kit version change, or a missing manifest, triggers a full build.
  • An incremental build's output is byte-identical to a full build's.

References

  • #1010: incremental builds with a separate cache, plus its documented limits
  • #1183, #1184: deterministic output
  • Eleventy's --incremental: rebuilds a changed template and whatever depends on it, and does a full build when the config changes
  • Jekyll's incremental regeneration: a .jekyll-metadata file of dependencies; it misses pages that list other pages, which is our sidebar problem
  • Sphinx: only re-reads new or changed sources, keeping its parsed environment next to the build output
  • Next.js Incremental Static Regeneration: regenerates single static pages instead of rebuilding the site
Langage dominant
JavaScript
Étoiles
70
Forks
75
Merge moyen
2 j 12 h
PR mergées (30 j)
50

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/doc-kit

Toutes les issues de nodejs/doc-kit

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.