test(api): freeze the public package surface before 1.0 - #36
Conversation
ea601e3 to
d94e984
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d94e9844fd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } | ||
|
|
||
| function renderSnapshot(): string { | ||
| const declarations = declarationFiles(typesRoot); |
There was a problem hiding this comment.
The snapshot is generated exclusively from the hand-maintained packages/causescope/types directory and the manifest, while the package build does not generate declarations from packages/causescope/src. Consequently, adding a named export to any source entrypoint—or changing its implementation signature without updating the corresponding checked-in .d.ts—leaves generatedSnapshot unchanged, so pnpm check can pass despite the published JavaScript and declaration surfaces drifting. Derive declarations from the entrypoint sources or explicitly compare each built module's exports against its declarations before accepting the snapshot.
Useful? React with 👍 / 👎.
1 participant
Summary
pnpm checkon unreviewed package-surface drift with a concise first-difference reportValidation
pnpm verify:public-apipnpm docs:buildpnpm checkweimob,fypro, local username, or npm-token patternCloses #35