Ability to specify which config files are read (--config)

[jonasb]

I have a project with both evalite.config.ts and vitest.config.ts. I expect evalite to only read evalite.config.ts, but that is not the case.

My vitest.config.ts looks like this, which is incompatible with evalite:

import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";

export default defineWorkersConfig({
  test: {
    poolOptions: {
      workers: {
        wrangler: {
          configPath: "./wrangler.test.jsonc",
        },
      },
    },
  },
});

My evalite.config.ts file:

import { defineConfig } from "evalite/config";

export default defineConfig({});

evalite: 0.18.0

[dkokotov]

Fwiw, I'm actually relying on this because in my vitest.config.ts I configure alias resolution so the imports in my monorepo resolve correctly.

Vitest supports overriding the name of the config file, maybe Evalite can expose this so you can have a different vitest config for Evalite vs "regular" Vitest.

[mattpocock]

Yeah, I think the default expected behavior should be for all Vitest options to fall through to Evalite.

However, I think we should allow a config flag that allows you to be specific about the config files that you want loaded.

[mattpocock]

@claude Come up with a proposal for how this would work, and a basic implementation plan we can look at later. Do not change the code, just add a comment to this issue.

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[mattpocock]

@jonasb @dkokotov What do you think of #303?

[dkokotov]

it seems reasonable. I am not using vitest other than as a dependency of evalite. so as long as there is some way for specifying vitest config (which #303 should allow), it's all good.

[jonasb]

@mattpocock Looks good to me, I like that it becomes explicit!

[mattpocock]

Closing this since it got fixed in the #240 branch