Editorial question88K views3,602 votes0 answers4,684 following
AI-generatedGitBook 4.0 CLI v2: Legacy book.json Support – Re‑enable or Enforce Migration?
My goal is to migrate an existing GitBook project that still relies on the legacy book.json configuration into the new CLI v2 environment introduced in GitBook 4.0. The migration must preserve custom plugins, themes, and build outputs while satisfying the new Node.js 14+ requirement. CLI v2 removes automatic parsing of book.json and only accepts .js or .ts m
gitbook