v1 #240
Open
v1 #240
Conversation
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
🦋 Changeset detectedLatest commit: 0a79b3a The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
commit: |
Owner
Author
|
@claude Remove the BACKEND_ONLY_CONSTANT import that's causing the error in CI |
|
Claude finished @mattpocock's task —— View job Task completed
Fixed the CI error: The error was caused by imports from
The changes have been committed and pushed to the |
This was referenced Oct 21, 2025
mattpocock
force-pushed
the
v1
branch
3 times, most recently
from
c69a19d to
4ae1080
Compare
This was referenced Nov 9, 2025
- Remove unused DB_LOCATION import from test-utils.ts - Replace FILES_LOCATION import with local constant in files.test.ts Co-authored-by: Matt Pocock <mattpocock@users.noreply.github.com>
- Add dotenv as a dependency - Create env-setup-file module that imports dotenv/config - Export env-setup-file as 'evalite/env-setup-file' - Automatically prepend env-setup-file to setupFiles array - Update documentation to reflect automatic .env loading - Update example config to remove manual dotenv setup Fixes #234 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Matt Pocock <mattpocock@users.noreply.github.com>
… precedence - Add loadVitestSetupFiles() to load setupFiles from vitest.config.ts - Merge setupFiles from both configs with evalite.config.ts taking precedence - Add tests for vitest.config.ts setupFiles support and precedence - setupFiles execution order: env-setup-file -> vitest -> evalite Co-authored-by: Matt Pocock <mattpocock@users.noreply.github.com>
…awns a custom UI.
…n specific variants.
… and description are now automatically extracted from the scorer's return value.
…ers must now explicitly pass Vite config via evalite.
Vitest workspace configs cause evalite to pick up wrong files. Test demonstrates: - Unit tests run when they shouldn't - Eval files ignored - Workspace include patterns override evalite patterns Refs #95 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
* Wrote the scorers docs * Removed all references to autoevals * Fixed CI * Updates * Docs updates and storage * Re-added redirects
* Updated CI to run on PR's * Made the push only run on v1 and main * Fixed file
* refactor: evalite.each to support a skip modifier and add corresponding tests Solves: #318 * Create late-dryers-repair.md --------- Co-authored-by: Matt Pocock <mattpocockvoice@gmail.com>
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.
No description provided.