Skip to content
← Back to activity

Immutable solution version

Node.js OSS mem0: Supabase, Redis, and pgvector setup all fail

Version 1Sign in to save

Complete solution

All three were fixed and the issue closed as resolved, per maintainer kartik-mem0. (1) Supabase PGRST205: the memory_migrations table lookup is now handled with a graceful fallback, but you still have to run the SQL migration from the Supabase provider docs against your project yourself; the docs steps alone did not create that table.

Mem0 - Several things break in the Node.js OSS version of mem0 at once.

The fix

All three were fixed and the issue closed as resolved, per maintainer kartik-mem0. (1) Supabase PGRST205: the memory_migrations table lookup is now handled with a graceful fallback, but you still have to run the SQL migration from the Supabase provider docs against your project yourself; the docs steps alone did not create that table. (2) Redis toString crash: fixed in an earlier PR by setting embedding dims properly in the constructor, so upgrade the mem0 package and pass your embedding dims explicitly in the Redis vector-store config. (3) pgvector: it was genuinely missing from the factory and was added in PR #3997 (merged), so upgrade to a release that includes it before trying to configure pgvector as your store.

Thread: gh:mem0ai/mem0#3491

Evidence

In gh:mem0ai/mem0#3491 (https://github.com/mem0ai/mem0/issues/3491), the issue reported: Several things break in the Node.js OSS version of mem0 at once. With Supabase you get "Could not find the table 'public.memorymigrations' in the schema cache" (PGRST205) even when following the Supabase provider docs exactly. With Redis, creating the index fails with "cannot read properties of undefined (reading 'toString')". And pgvector is documented as a vector store option but is missing from the factory entirely, so it cannot be configured. The verified answer: All three were fixed and the issue closed as resolved, per maintainer kartik-mem0. (1) Supabase PGRST205: the memorymigrations table lookup is now handled with a graceful fallback, but you still have to run the SQL migration from the Supabase provider docs against your project yourself; the docs steps alone did not create that table. (2) Redis toString crash: fixed in an earlier PR by setting embedding dims properly in the constructor, so upgrade the mem0 package and pass your embedding dims explicitly in the Redis vector-store config. (3) pgvector: it was genuinely missing from the factory and was added in PR #3997 (merged), so upgrade to a release that includes it before trying to configure pgvector as your store.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_uNxaARXvMvzsE8VBwVUSTQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Node.js OSS mem0: Supabase, Redis, and pgvector setup all fail <span>— Vectle</span></a>