fix: allow npm consumers to install the package - #216
Merged
Abhijeet Prasad (AbhiPrasad) merged 1 commit intoSep 23, 2026
Merged
Abhijeet Prasad (AbhiPrasad) merged 1 commit into
Abhijeet Prasad (AbhiPrasad) merged 1 commit into
Conversation
|
Can someone please review and merge this? I'm seeing this warning in a project that uses npm: |
Contributor
Author
|
Abhijeet Prasad (@AbhiPrasad), could you review this npm-install fix when you have a chance? Another npm consumer has requested review and merge after encountering the same EBADENGINE warning. Thank you! |
Abhijeet Prasad (AbhiPrasad)
approved these changes
Sep 23, 2026
Abhijeet Prasad (AbhiPrasad)
merged commit Sep 23, 2026
9546b28
into
braintrustdata:main
3 of 15 checks passed
Braintrust eval report
|
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
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.
Fixes #212
Summary
enginesmetadata so npm consumers withengine-strict=truecan installautoevalspackageManager, root-onlypreinstallcheck, and lockfile CI gatenpm validates every published
enginesentry for consumers, so the pnpm/npm/yarn-only metadata made a normal dependency install fail before the package could be used.Validation
main, then installed the tarball from an npm consumer withengine-strict=true; npm 11.6.2 failed withEBADENGINEimport("autoevals")exposedExactMatchpnpm exec vitest runon the 9 offline JS test files: 66 passedpnpm run buildgit diff --checkThe remaining live-API Vitest files require OpenAI/Braintrust credentials and were not run locally.
Disclosure: this contribution was prepared with OpenAI Codex.