v3.8.0

A minor release for testing RAG in TypeScript: the answer matchers now compile with types, and a new guide shows the whole setup with Vitest. No breaking changes.

npm install @devilsdev/rag-pipeline-utils@^3.8.0

Added

• Typed matchers for TypeScript. @devilsdev/rag-pipeline-utils/testing exports RagMatchers, the signatures of toBeGroundedIn, toCite and toContainNoPII on expect. Add them to Vitest's or Jest's Matchers in a declaration file and the matchers compile, with a wrong argument reported as a type error. Until now expect(result).toBeGroundedIn() didn't compile in TypeScript, and the declaration the Testing page suggested failed under Vitest 5. Matchers in TypeScript

  import "vitest";
  import type { RagMatchers } from "@devilsdev/rag-pipeline-utils/testing";
  
  declare module "vitest" {
    interface Matchers<R, T> extends RagMatchers<R> {}
  }

• A "Testing RAG in TypeScript" guide: typed matchers on an offline test pipeline, catching a wrong number with checkAnswer, and a test set scored by rag-pipeline eval in CI. It is built from a runnable project, examples/testing-typescript, which is type-checked, tested and evaluated with the latest Vitest and TypeScript before each release. The guide

Internal

• Releases announce themselves on GitHub Discussions, dev.to, Bluesky and Mastodon, from the release notes and blog post, after checks on every number and link.
• Development dependencies lost 237 packages: eight unused OpenTelemetry SDK packages and three modules nothing loaded. npm audit findings in development tooling fell from 64 to 14, none high. What you install had none and still has none.

The scoped packages, @devilsdev/rag-mcp-server and create-rag-pipeline are released at 3.8.0 too. Full details: CHANGELOG · Blog post