Node/TypeScript port (memU-js) — sharing and feedback

[RenKoya1]

Summary

I built a Node/TypeScript port of memU (memU-js) so JS/TS teams can use memU without a Python bridge. I’d
like feedback on scope and how you’d like to integrate or reference it.

Motivation

Node/TS is common in production. A TS port reduces integration cost, improves DX with types, and makes
customization easier.

Customization highlights

• Prompt customization (memory-type / retrieve / preprocess)
• Workflow pipeline/steps can be extended or swapped
• LLM profiles per use case with provider:model format
• Storage backends selectable (in-memory / SQLite / Postgres)

What’s included

• Core memory service, workflows, settings, prompts
• Multi-provider LLM integration via Vercel AI SDK
• In-memory, SQLite, and PostgreSQL (Prisma) support
• Tests and TypeScript build setup

Scope / Limitations

• Postgres requires Prisma migrations
• SQLite auto-creates schema on first run
• In-memory requires no setup

Questions

• Would you prefer memU-js as a subdirectory in this repo or a separate repo?
• Should we link memU-js from the main README and docs?
• Any scope changes or missing pieces you’d like before announcing it?

https://github.com/RenKoya1/memU-js

[hamzakarambiri-arch]

Hello,
I’m interested in helping as a support or contributor on this project.
I’m available to assist users, test features, and answer questions.

How can I help?
Thank you.

[shyamshm777]

thanks

[lacabiont-lgtm]

thanks

Bv

[RenKoya1]

@sairin1202
I'd appreciate it if you could answer the questions.