Cannot find package 'drizzle-orm' (using packages individually)

[peterjskaltsis]

Awesome work putting this together!

Not sure if this is intended, but thought I'd report it... looks like the memory package is a dep of the agents package?

If you only install agents, you get an error about needing subdeps of memory.

[dev] Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'drizzle-orm' imported from /Users/ps/Developer/my-project/node_modules/.pnpm/@ai-sdk-tools+memory@0.1.0/node_modules/@ai-sdk-tools/memory/dist/index.js

[pontusab]

I will update this, the agent requires the memory package actually, it's for workingContext etc. But you should not need to use a provider, default is in memory.

[peterjskaltsis]

Legend!

[brunnolou]

I was using only the agent without memory import { Agent } from "@ai-sdk-tools/agents";

And still got the error:

// Module not found: Can't resolve 'drizzle-orm'
  1 | // src/providers/drizzle.ts
> 2 | import { desc, eq } from "drizzle-orm";
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

It feels wrong...
Is drizzl-orm needed even if I only use the InMemoryProvider solution?

[peterjskaltsis]

@pontusab looks like the underlying cause is that the memory package’s barrel statically imports the Drizzle provider, which forces drizzle-orm resolution even when it’s marked optional.

I think the cleanest fix would be to export providers via subpaths rather than from the root barrel — for example:

// instead of this:
import { DrizzleProvider } from '@ai-sdk-tools/memory'

// allow this:
import { DrizzleProvider } from '@ai-sdk-tools/memory/drizzle'

That way only users who explicitly import the Drizzle provider pull in drizzle-orm, and those using only InMemoryProvider or others don’t need the dependency installed at all.

Happy to open a small PR to adjust the exports if you'd be open to this?

[pontusab]

yeah! now when the big pr is merged feel free to help me 🙌

[peterjskaltsis]

yeah! now when the big pr is merged feel free to help me 🙌

Still trying to get local working 100% to test the changes, but I've got a proposal PR open now #66