[Bug]: @chroma-core/google-gemini publishes test files to npm, breaking Next.js Turbopack

[bhargavrakholiya123]

What happened?

The @chroma-core/google-gemini package currently includes raw testing files (specifically src/index.test.ts) when published to the npm registry.

When importing this package into a strict build environment like Next.js 15+ with Turbopack, it triggers a hard build crash because the bundler attempts to parse the uncompiled test file.

Steps to reproduce:

1. Create a Next.js 16+ application with Turbopack.
2. Run npm install @chroma-core/google-gemini.
3. Import the function: import { GoogleGeminiEmbeddingFunction } from "@chroma-core/google-gemini";
4. Run npm run dev.

Expected behavior:
The package should be published to npm without **/*.test.ts files (e.g., by adding them to .npmignore or the tsconfig.json exclude array).

(Note: I wanted to submit a PR for this, but as of right now, the source code for the google-gemini package doesn't seem to be in the clients/js/packages folder of this monorepo yet!)

Versions

Next.js: 16.1.6 (Turbopack)
Package: @chroma-core/google-gemini (latest)
OS: Windows

Relevant log output

File causing the crash: node_modules/@chroma-core/google-gemini/src/index.test.ts

Missing module type
The module type effect must be applied before adding Ecmascript transforms

[xXMrNidaXx]

This is a common issue with npm packages that include test files - Next.js Turbopack tries to compile everything.

Quick workarounds:

1. Exclude in next.config.js:

module.exports = {
  experimental: {
    turbo: {
      resolveExtensions: ['.tsx', '.ts', '.jsx', '.js'],
    }
  },
  webpack: (config) => {
    config.module.rules.push({
      test: /\.test\.(ts|js)x?$/,
      use: 'ignore-loader'
    });
    return config;
  }
}

2. Use npm overrides to patch:

{
  "overrides": {
    "@chroma-core/google-gemini": "chroma-core/google-gemini"
  }
}

3. Import specifically (avoid barrel exports):

// Instead of
import { something } from '@chroma-core/google-gemini';
// Try direct path
import { something } from '@chroma-core/google-gemini/dist/something';

The real fix should be adding .npmignore or updating files in package.json on the chroma side to exclude test files from published package.

[kylediaz]

Hi @bhargavrakholiya123
You're more than welcome to open a PR. @ me and I'll review as soon as possible.
The package is located here:
https://github.com/chroma-core/chroma/tree/main/clients/new-js/packages/ai-embeddings/google-gemini
(note the folder is new-js rather than js)

[kylediaz]

I saw your PR. I'll add it to my TODO to test it out