Background
@fedify/fixture is a monorepo-private workspace package and is not published to npm or JSR. Any non-test source file that imports it resolves fine inside the monorepo but fails once a depending package is installed from a registry.
The convention — confine @fedify/fixture imports to **/*.test.ts — is currently implicit. There is no contributor-facing documentation for the package, CONTRIBUTING.md does not mention the boundary, and nothing guards it automatically.
Proposal
- Add a contributor-facing README for
@fedify/fixture and a short pointer in CONTRIBUTING.md that states the boundary rule and its rationale.
- Add a checker, runnable via
mise, that flags any non-*.test.ts file in the monorepo importing or re-exporting from @fedify/fixture, and wire it into the aggregate mise run check. It is positioned as a contributor convenience, not as rigorous verification.
Assisted-by: Claude Code:claude-opus-4-7
Background
@fedify/fixtureis a monorepo-private workspace package and is not published to npm or JSR. Any non-test source file that imports it resolves fine inside the monorepo but fails once a depending package is installed from a registry.The convention — confine
@fedify/fixtureimports to**/*.test.ts— is currently implicit. There is no contributor-facing documentation for the package, CONTRIBUTING.md does not mention the boundary, and nothing guards it automatically.Proposal
@fedify/fixtureand a short pointer in CONTRIBUTING.md that states the boundary rule and its rationale.mise, that flags any non-*.test.tsfile in the monorepo importing or re-exporting from@fedify/fixture, and wire it into the aggregatemise run check. It is positioned as a contributor convenience, not as rigorous verification.Assisted-by: Claude Code:claude-opus-4-7