langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 20:35:34 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[GH-ISSUE #3603] [langgraph]: Add JavaScript checkpointer integrations section (with BetterDBSaver as first entry) #2742

New Issue
Open
opened 2026-06-05 17:26:35 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 17:26:35 -04:00
Owner
Copy Link
Copy Source

Originally created by @KIvanow on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/langchain-ai/docs/issues/3603

Type of issue

request for content

Language

JavaScript

Description

Summary

I'd like to contribute integration docs for @betterdb/agent-cache, a Valkey/Redis-backed multi-tier cache for AI agent workloads with adapters for LangChain (BaseCache), LangGraph (BaseCheckpointSaver), and Vercel AI SDK. Opening this issue before the PR because one piece creates a new directory and would resolve an existing broken nav reference, both of which warrant a quick structural check with maintainers.

Package: https://www.npmjs.com/package/@betterdb/agent-cache

Findings during investigation

  1. src/oss/javascript/integrations/checkpointers/ does not exist. There is no JS-side equivalent of src/oss/python/integrations/checkpointers/index.mdx.
  2. src/docs.json references oss/javascript/langgraph/persistence in the JS nav, but the file src/oss/javascript/langgraph/persistence.mdx does not exist on disk. That reference is broken today.
  3. src/oss/javascript/integrations/llm_caching/ exists and currently has one entry (azure_cosmosdb_nosql.mdx). This is the natural home for BetterDBLlmCache.

Proposed changes

  1. src/oss/javascript/integrations/checkpointers/index.mdx (new directory) JS-side parallel to the Python checkpointers index. Table format:
    backend | package | source. Would include existing savers (MemorySaver, PostgresSaver, SqliteSaver, community checkpoint-redis, etc.) plus BetterDBSaver, so the section is complete rather than a one-row placeholder.

  2. src/oss/javascript/integrations/llm_caching/betterdb.mdx Integration page for BetterDBLlmCache with ChatOpenAI, matching the azure_cosmosdb_nosql.mdx template.

  3. src/oss/javascript/integrations/providers/betterdb.mdx + entry in all_providers.mdx under "LLM caching" and a new "Checkpointers" section if appropriate.

  4. src/docs.json nav updates for the new pages. Would also resolve the broken oss/javascript/langgraph/persistence reference, either by removing it or pointing it to the new checkpointers index.

Scope note

@betterdb/agent-cache is JavaScript/TypeScript only, no Python equivalent. Pages would be scoped to the JavaScript tab, following the precedent set by the existing JS-only llm_caching/ section.

Questions before I start the PR

  1. Is creating src/oss/javascript/integrations/checkpointers/ the preferred approach, or would you rather the JS content be added as :::js fences inside the existing Python checkpointers/index.mdx?
  2. For the broken langgraph/persistence nav reference: remove it, or redirect to the new checkpointers index?
  3. One bundled PR covering all three pages, or split into separate PRs?

Happy to adjust based on your preferences. If there's a lighter-touch path, let me know.

Originally created by @KIvanow on GitHub (Apr 16, 2026). Original GitHub issue: https://github.com/langchain-ai/docs/issues/3603 ### Type of issue request for content ### Language JavaScript ### Description ## Summary I'd like to contribute integration docs for `@betterdb/agent-cache`, a Valkey/Redis-backed multi-tier cache for AI agent workloads with adapters for LangChain (BaseCache), LangGraph (BaseCheckpointSaver), and Vercel AI SDK. Opening this issue before the PR because one piece creates a new directory and would resolve an existing broken nav reference, both of which warrant a quick structural check with maintainers. Package: https://www.npmjs.com/package/@betterdb/agent-cache ## Findings during investigation 1. `src/oss/javascript/integrations/checkpointers/` does not exist. There is no JS-side equivalent of `src/oss/python/integrations/checkpointers/index.mdx`. 2. `src/docs.json` references `oss/javascript/langgraph/persistence` in the JS nav, but the file `src/oss/javascript/langgraph/persistence.mdx` does not exist on disk. That reference is broken today. 3. `src/oss/javascript/integrations/llm_caching/` exists and currently has one entry (`azure_cosmosdb_nosql.mdx`). This is the natural home for `BetterDBLlmCache`. ## Proposed changes 1. **`src/oss/javascript/integrations/checkpointers/index.mdx`** (new directory) JS-side parallel to the Python checkpointers index. Table format: backend | package | source. Would include existing savers (`MemorySaver`, `PostgresSaver`, `SqliteSaver`, community `checkpoint-redis`, etc.) plus `BetterDBSaver`, so the section is complete rather than a one-row placeholder. 2. **`src/oss/javascript/integrations/llm_caching/betterdb.mdx`** Integration page for `BetterDBLlmCache` with `ChatOpenAI`, matching the `azure_cosmosdb_nosql.mdx` template. 3. **`src/oss/javascript/integrations/providers/betterdb.mdx`** + entry in `all_providers.mdx` under "LLM caching" and a new "Checkpointers" section if appropriate. 4. **`src/docs.json` nav updates** for the new pages. Would also resolve the broken `oss/javascript/langgraph/persistence` reference, either by removing it or pointing it to the new checkpointers index. ## Scope note `@betterdb/agent-cache` is JavaScript/TypeScript only, no Python equivalent. Pages would be scoped to the JavaScript tab, following the precedent set by the existing JS-only `llm_caching/` section. ## Questions before I start the PR 1. Is creating `src/oss/javascript/integrations/checkpointers/` the preferred approach, or would you rather the JS content be added as `:::js` fences inside the existing Python `checkpointers/index.mdx`? 2. For the broken `langgraph/persistence` nav reference: remove it, or redirect to the new checkpointers index? 3. One bundled PR covering all three pages, or split into separate PRs? Happy to adjust based on your preferences. If there's a lighter-touch path, let me know.
yindo added the langgraphexternal labels 2026-06-05 17:26:35 -04:00
yindo commented 2026-06-05 17:26:35 -04:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Apr 16, 2026):

Please update the title of this issue.

The current title contains the default placeholder text. A descriptive title helps maintainers understand and prioritize your issue.

Good titles:

  • "Missing example for streaming with tool calls"
  • "Typo in LangGraph quickstart guide"
  • "Add documentation for SummarizationMiddleware"

Please edit the title to briefly describe your issue. Until then, this issue may not receive attention from maintainers.

Thank you for contributing!

<!-- gh-comment-id:4260472969 --> @github-actions[bot] commented on GitHub (Apr 16, 2026): <!-- default-title-check --> **Please update the title of this issue.** The current title contains the default placeholder text. A descriptive title helps maintainers understand and prioritize your issue. **Good titles:** - "Missing example for streaming with tool calls" - "Typo in LangGraph quickstart guide" - "Add documentation for SummarizationMiddleware" **Please edit the title** to briefly describe your issue. Until then, this issue may not receive attention from maintainers. Thank you for contributing!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label external langgraph
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#2742
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?