Issue with Langgraph CLI version 0.0.15 and above on Windows #2

Closed
opened 2026-02-16 04:16:53 -05:00 by yindo · 6 comments
Owner

Originally created by @KeenanFernandes2000 on GitHub (Mar 20, 2025).

Originally assigned to: @dqbd on GitHub.

I have been using the Langgraph CLI since my issue got resolved in version 0.0.10.

I decided to use the latest version of it being 0.0.17 and it throws an error that doesn't have anything to do with my graphs in particular. I manually tested each version backwards and found this error all the way back from version 0.0.15.

I am using version 0.0.14 which works perfectly, but wanted to bring this to the devs attention.


Error:
.../AppData/Local/npm-cache/_npx/67c725d45ea9c1da/node_modules/@langchain/langgraph-api/dist/stream.mjs:3
import { Command, Send, } from "@langchain/langgraph";
^^^^^^^
SyntaxError: The requested module '@langchain/langgraph' does not provide an export named 'Command'
at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5)

Node.js v20.18.0

Originally created by @KeenanFernandes2000 on GitHub (Mar 20, 2025). Originally assigned to: @dqbd on GitHub. I have been using the Langgraph CLI since my issue got resolved in version 0.0.10. I decided to use the latest version of it being 0.0.17 and it throws an error that doesn't have anything to do with my graphs in particular. I manually tested each version backwards and found this error all the way back from version 0.0.15. I am using version 0.0.14 which works perfectly, but wanted to bring this to the devs attention. --- Error: .../AppData/Local/npm-cache/_npx/67c725d45ea9c1da/node_modules/@langchain/langgraph-api/dist/stream.mjs:3 import { Command, Send, } from "@langchain/langgraph"; ^^^^^^^ SyntaxError: The requested module '@langchain/langgraph' does not provide an export named 'Command' at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21) at async ModuleJob.run (node:internal/modules/esm/module_job:229:5) at async ModuleLoader.import (node:internal/modules/esm/loader:473:24) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5) Node.js v20.18.0
yindo closed this issue 2026-02-16 04:16:53 -05:00
Author
Owner

@benjamincburns commented on GitHub (Apr 28, 2025):

cc @dqbd

@benjamincburns commented on GitHub (Apr 28, 2025): cc @dqbd
Author
Owner

@benjamincburns commented on GitHub (Apr 28, 2025):

@KeenanFernandes2000 Thanks for reporting - can you please share a bit more detail about what steps you're taking to trigger the error that you're seeing? What CLI commands are you running? Does it behave this way on any project in your environment, or only specific ones? If specific ones, what is unique about those projects?

@benjamincburns commented on GitHub (Apr 28, 2025): @KeenanFernandes2000 Thanks for reporting - can you please share a bit more detail about what steps you're taking to trigger the error that you're seeing? What CLI commands are you running? Does it behave this way on any project in your environment, or only specific ones? If specific ones, what is unique about those projects?
Author
Owner

@KeenanFernandes2000 commented on GitHub (Apr 28, 2025):

Image

I just run the npx command provided on the docs, I guess the same issue still persists in version 0.0.29


Just for reference it works when I use version 0.0.14

Image

@KeenanFernandes2000 commented on GitHub (Apr 28, 2025): ![Image](https://github.com/user-attachments/assets/7b29c01f-b2c8-4ec3-8889-3785a491e4e7) I just run the npx command provided on the docs, I guess the same issue still persists in version 0.0.29 --- Just for reference it works when I use version 0.0.14 ![Image](https://github.com/user-attachments/assets/6f21036b-8849-4d90-8955-2c1de49e5b26)
Author
Owner

@benjamincburns commented on GitHub (May 8, 2025):

Hmm, it's a bit strange that 0.0.14 works but 0.0.17 doesn't. @dqbd would know better than me, but when I do a git diff to find all changes in the langchain-cli directory between 0.0.14 and 0.0.17 I see no changes other than the version number.

We unforunately don't have version tags, but I found the commit hashes - here's the full command:

git diff b7a23ebdabb8fa9deaacdf3e52ec049d74c9d4ae..b7b21f89c441fb7b1f4772dc1a5d5c5d9228be7e -- libs/langgraph-cli
@benjamincburns commented on GitHub (May 8, 2025): Hmm, it's a bit strange that 0.0.14 works but 0.0.17 doesn't. @dqbd would know better than me, but when I do a `git diff` to find all changes in the `langchain-cli` directory between 0.0.14 and 0.0.17 I see no changes other than the version number. We unforunately don't have version tags, but I found the commit hashes - here's the full command: ``` git diff b7a23ebdabb8fa9deaacdf3e52ec049d74c9d4ae..b7b21f89c441fb7b1f4772dc1a5d5c5d9228be7e -- libs/langgraph-cli ```
Author
Owner

@benjamincburns commented on GitHub (May 8, 2025):

@KeenanFernandes2000 given my previous comment, has anything changed on your end, e.g. tsconfig.json, lockfile bump, etc? Does 0.0.14 still work today and 0.0.17 still fail?

@benjamincburns commented on GitHub (May 8, 2025): @KeenanFernandes2000 given my previous comment, has anything changed on your end, e.g. `tsconfig.json`, lockfile bump, etc? Does `0.0.14` still work today and `0.0.17` still fail?
Author
Owner

@dqbd commented on GitHub (May 20, 2025):

Hello @KeenanFernandes2000! We're now using the @langchain/langgraph version found in your project, so would recommend upgrading the version in your project

@dqbd commented on GitHub (May 20, 2025): Hello @KeenanFernandes2000! We're now using the `@langchain/langgraph` version found in your project, so would recommend upgrading the version in your project
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/langgraphjs-api#2