I’m considering evaluating LangGraph, specifically the JavaScript version.
However, I have some concerns:
What’s the official stance or current level of support for the JavaScript version?
Hey @ilann!
LG.js is absolutely a first class citizen. The python package is admittedly ahead just by virtue of the fact that the python package has led the narrative for both LC and LG, but we’re actively working to expand our efforts there.
On the docs front – we’re not a fan of lg.js docs in its current state either (picture related). We’re working to completely overhaul these in the next month or so. We of course think it’s still worthwhile to invest in LG.js in anticipation of this, but we’re obviously biased.
+1 LG.js. Would be fun to see LG.py / LG.js usage metrics. (Also useful to know how behind is LG.js)
As for usage metrics you can cross compare download counts for the libraries (that’s how we track things anyways). If we’re going feature-for-feature, the two releases aren’t actually that far off from each other.
Oh - nice tip. Yes looks like LG.js 1.8M Vs LG.py 4.3M per month. I think I have my candidate even if in terms of features they are similar. thanks for pointing this to me 
do you mean there is another library you’re reaching for instead of LG.js? (would love to know what it is/ why if thats the case 
)
I only know these two (Python and JS) GitHub - langchain-ai/langgraph: Build resilient language agents as graphs. and GitHub - langchain-ai/langgraphjs: Framework to build resilient language agents as graphs. My use case will be an onboarding workflow. A chat that will drive users during the platform onboarding. I will need graphs to represent the story and its multiple paths, state, checkpoints, memory and maybe something more. lets see
Learning LC-LG with the OG Docs has been quite the experience, looking forwards for the overhauled version.
