Skip to content

History / ⭐ Package Manifests

Revisions

  • Correct a bad fix from 2026-08-20: restore 43 package.json files The 2026-08-20 workspace-count sweep incorrectly collapsed this page's own file-count breakdown (43 total, including 2 real non-workspace test-fixture manifests under tests/blackbox/extensions/) into the unrelated "40 workspace packages" metric, dropping the fixtures as if they were phantom. They're real files, confirmed present in both this fork and upstream. todo.md's own "Package manifest migration" section had the correct 43/6 numbers the whole time and was never touched - this page just needed to match it, now with the two metrics explicitly disambiguated so this doesn't get conflated again.

    @Terrence721 Terrence721 committed Aug 23, 2026
  • Fix workspace package count: 40, not 42/43 Verified against root package.json's workspaces glob and upstream's identical pnpm-workspace.yaml. Also drops 2 phantom "extension fixture" packages from the Package Manifests table's tests/* row — there are only 4 real tests/* package.json files, confirmed directly against both this fork and the upstream reference source. Syncs the workflow count (17, not 18) and packages/types file count (43 of ~54) to match the main repo, already corrected there.

    @Terrence721 Terrence721 committed Aug 20, 2026
  • Add wiki: architecture, Yarn migration, package manifests, CI/Docker, known gaps

    @Terrence721 Terrence721 committed Aug 17, 2026