Skip to content

Commit dee218a

Browse files
noreplyclaude
andcommitted
fork: schema check guards package.json and refuses imports it cannot resolve
- The package.json of every workspace package that schema code imports is guarded, so an edit that re-points such an import (another export target, a condition Node picks first, exports removed in favour of main) is refused. Every file any export condition can pick is guarded, and main, module and types are followed when a package has no exports. - An import that should resolve inside the repository but does not is refused, naming the import: a workspace package with no entry file, a relative import of a missing file, a #name import, a computed import() or require(), import.meta.glob. Only packages outside the workspace resolve to nothing; the output lists them. - Workspace packages come from the pnpm workspace list (scoped or not, at any depth), and a change to that list is refused. A test-path file that schema code imports is guarded like any other. - The tracer no longer counts the key in `export const { S: renamed }` as declaring S. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent ca47142 commit dee218a

2 files changed

Lines changed: 616 additions & 96 deletions

File tree

0 commit comments

Comments
 (0)