Repository navigation
Commit 5c2688e
fork: schema check guards the importer's dependency specs and judges only new unfollowable imports
- The dependency specs of every name schema code imports (workspace packages and outside names
such as effect) are compared in the package.json files of the packages holding schema code and
the root one, plus pnpm-workspace.yaml catalog/catalogs/overrides/patchedDependencies and the
root pnpm.overrides/patchedDependencies/resolutions. Patch files of those names are guarded.
Other dependency changes stay free.
- A package.json is judged by the fields that map the imports schema code makes through it
(name, type, main/module/types/browser, imports, the export entries answering those keys), so
adding a module to a package stays free.
- An import the check cannot follow is refused only when the branch brings it; ones already on
the merge-base are listed, not refused. Imports are read from code with comments and string
contents blanked, so prose like "require (in order)" is not an import.
- Tests: the browser fallback, the four importer-side probes and more, manifest field judging,
the lexer and the merge-base rule.
Co-Authored-By: Claude Opus 5.5 <[email protected]>1 parent dee218a commit 5c2688e
2 files changed
Lines changed: 690 additions & 86 deletions
0 commit comments