Fix for issue with Windows dashboard setup not detecting npm #219
Merged
scottpersinger merged 3 commits intosupercog-ai:mainfrom Jun 10, 2025
Merged
Fix for issue with Windows dashboard setup not detecting npm #219scottpersinger merged 3 commits intosupercog-ai:mainfrom
scottpersinger merged 3 commits intosupercog-ai:mainfrom
Conversation
scottpersinger
approved these changes
Jun 10, 2025
Fixed a few typos
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Issue with npm not being detected on Windows when attempted to setup the Supercog dashboard, even when they are properly installed and PATH is configured. Returns error "npm or node not detected".
Change
in src/agentic/dashboard/setup.py, imported os library, then changed the subprocess command of "npm" to "npm.cmd" if the os.name is "nt" (windows) instead of "posix" (unix/linux/mac)
The reason this bug exists is because on Windows, command-line executables installed via npm (like npm, npx, etc.) are typically provided as .cmd files (e.g., npm.cmd) in the system PATH:
Windows does not natively recognize scripts without an extension as executable.
The .cmd extension tells the Windows shell to run the file as a command script.
On Unix-like systems (Linux/macOS), the executable is just npm (no extension).
See #206