You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure where the best place to put this is as I can't find the actual code for the LangGraph API server/LangGraph Studio and figure its not on GitHub
Issue:
I have a graph defined within a monorepo and have my langgraph.json file in the root of my repository. My langgraph configuration looks like:
I found that I can get the graph to build and load into studio, but that my Input form was not rendering properly -- I could only enter raw input i.e. { messages: [{...}]} instead of the nice form with the ability to select Human, AI, System, etc.
and noticed that it is only taking into account the @langchain/langgraph package, whereas the BaseMessage types are in @langchain/core. Updating the conditional to:
Hi folks,
Not sure where the best place to put this is as I can't find the actual code for the LangGraph API server/LangGraph Studio and figure its not on GitHub
Issue:
I have a graph defined within a monorepo and have my
langgraph.json
file in the root of my repository. My langgraph configuration looks like:I found that I can get the graph to build and load into studio, but that my Input form was not rendering properly -- I could only enter raw input i.e.
{ messages: [{...}]}
instead of the nice form with the ability to selectHuman
,AI
,System
, etc.Bad build:
Expected build:
Checking my logs I found warnings of:
I tracked this down to the
/api/langgraph_api/js/src/parser/parser.mts
in the API server container:and noticed that it is only taking into account the
@langchain/langgraph
package, whereas theBaseMessage
types are in@langchain/core
. Updating the conditional to:seems to resolve the issue. My current workaround is creating a patch file:
and including the patch in my dockerfile lines:
I'm happy to submit a patch for this, but if that's not possible, hope this report helps resolve on yourside. Thanks.
The text was updated successfully, but these errors were encountered: