Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to run on windows #320

Open
verajosemanuel opened this issue May 31, 2024 · 5 comments
Open

unable to run on windows #320

verajosemanuel opened this issue May 31, 2024 · 5 comments

Comments

@verajosemanuel
Copy link

installed with no issue in windows gitbash (MYSYS) when running nb i get an error

$ nb
bash: C:\Users\joe\Anaconda3\Library\c\Users\joe\AppData\Roaming\npm/node_modules/nb.sh/nb: No such file or directory
@Rooyca
Copy link
Contributor

Rooyca commented Jun 4, 2024

Do you have Node.js installed?
Have you try using WSL?

@verajosemanuel
Copy link
Author

Yes. Node.js is installed. WSL is out of the available options

@xwmx
Copy link
Owner

xwmx commented Jun 4, 2024

@verajosemanuel The path separators switch from backslashes to forward slashes in the path to the executable. Is that a factor?

@verajosemanuel
Copy link
Author

Not sure. It is just the message when installing and trying to execute nb

@xwmx
Copy link
Owner

xwmx commented Jun 5, 2024

@verajosemanuel I don't currently have access to a windows machine so I'm going off memory and googling.

It's not yet clear to me where the path is coming from exactly. That path might be generated in your npm configuration. The first part is a Windows path, C:\Users\joe\Anaconda3\Library\c\Users\joe\AppData\Roaming\npm, which appears to be a standard location for locally-installed modules on Windows. The rest of the path, /node_modules/nb.sh/nb, is a unix-style path to the executable in a subfolder. This suggests there is code somewhere that is combining a Windows-style path with a unix-style path, then attempting to use it in Bash which expects unix-style paths, causing it to not work.

This path might be generated in an npm configuration file either in Windows or the unix environment running Bash. I recommend looking into that and seeing if you can identify the cause and a resolution. Let me know if this helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants