feat: a require condition for grounding and registry — jest consumers need no workaround - #21
Merged
Conversation
… need no workaround OrangeCat's jest (ts-jest, CJS mode) cannot transform an ESM-only .js dependency — its config documents this in its own words, and it is the failure class that broke AOZ's Jest inside ai-forms in v0.3. The v0.4 lesson applies unchanged: fix it in the package, not with a per-adopter mapper. The two subpaths a test suite actually loads (grounding, registry) now ship a CommonJS twin in dist-cjs/ behind an exports require condition. A CJS loader resolves it automatically; every ESM consumer keeps resolving dist/ exactly as before. Scoped to those two subpaths on purpose: forms re-exports ai-forms, which is ESM-only, so a CJS twin there would promise a load it cannot deliver. cjs-condition.test.js pins both loaders serving the same surface AND the same verdict, and was mutation-proven: deleting the dist-cjs type marker fails it, rebuilding greens it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OrangeCat's jest (ts-jest, CJS mode) cannot transform an ESM-only .js
dependency — its config documents this in its own words, and it is the
failure class that broke AOZ's Jest inside ai-forms in v0.3. The v0.4 lesson
applies unchanged: fix it in the package, not with a per-adopter mapper.
The two subpaths a test suite actually loads (grounding, registry) now ship
a CommonJS twin in dist-cjs/ behind an exports require condition. A CJS
loader resolves it automatically; every ESM consumer keeps resolving dist/
exactly as before. Scoped to those two subpaths on purpose: forms re-exports
ai-forms, which is ESM-only, so a CJS twin there would promise a load it
cannot deliver.
cjs-condition.test.js pins both loaders serving the same surface AND the
same verdict, and was mutation-proven: deleting the dist-cjs type marker
fails it, rebuilding greens it.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01WqKqMnHQHSmkGFfc5t7Rxn