Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Juan Lopez
    @somedumbfox
    @coreybutler Yes, the E: drive is a physical hard drive. I am using Windows Command Prompt or Powershell as Administrator when I run into the error.
    I have tried using default settings with the Shadow patch release. I've also configured it to be a root folder on my C: drive to see if I get different results. But I still encounter the error.
    Also worth noting is NVM is (sometimes) changing the shortcut path on for nodejs. But occasionally the shortcut is deleted entirely and not replaced.
    Juan Lopez
    @somedumbfox
    If the shortcut is successfully changed, NPM can be called but it throws a "'Node' is not a recognized internal or external" error. So It's kinda like a partial config makes it through.
    Corey Butler
    @coreybutler
    @somedumbfox it does seem like something isn't getting configured correctly. NVM does change the location of the symlink. Do you have anything else in your PATH that could be pointing to a different version of Node, either an old install or even a different version manager?
    Juan Lopez
    @somedumbfox
    I've looked in my environment variables. I don't see anything out of the ordinary or pointing to old references of node. NVM is the only version manager I used so far. I'm not aware of any others compatible with windows.
    Annotation 2020-07-28 132253.png
    Annotation 2020-07-28 132218.png
    Here are my system and local Path configurations to see if you might spot something I'm not seeing.
    @coreybutler
    Juan Lopez
    @somedumbfox

    @coreybutler I stumbled upon the fix out of the blue. I noticed something about my command prompt that looked off when I launched it today that may have been there for months without me noticing.

    This stack exchange post explains it: https://superuser.com/questions/727316/error-in-command-line-the-system-cannot-find-the-path-specified

    Essentially it was an incorrect configuration for Command Prompt that caused this issue. Clearing out this value and relaunching CMD fixed my issue. Thank you for your time.

    Corey Butler
    @coreybutler
    @somedumbfox wow, that's pretty obscure. I'm glad you got it working, and I appreciate you posting your fix!
    Juan Lopez
    @somedumbfox

    Yeah, it is very obscure. When I saw the "The system cannot find the path specified." message at the top of the prompt, I kinda questioned my sanity at that point. I use powershell mostly (because of vscode) so that may explain why I never noticed it. When I cleared that value in the registry I noticed it was a single path value, to miniconda. Which I uninstalled when I realized I needed the full suit of annaconda.

    So this is a problem that can occur when console specific applications are uninstalled, and the program does not perform a clean uninstall. Which is definitely handy to know for troubleshooting in the future.

    Corey Butler
    @coreybutler
    @somedumbfox - indeed. I've added the link you provided to the FAQ in the project wiki.
    EduVencovsky
    @EduVencovsky

    Hi guys, can someone explain me how global packages works in nvm? For example, I'm in node version X and have a global package with a version A, when I change to node version Y, the global package is still there with version A. Why is that? Shouldn't the global package only exists in the node version I installed it? Or have different global package version for each nove version?

    Thanks for everything, nvm is awesome

    EduVencovsky
    @EduVencovsky
    image.png
    For example, why when I install a new version, there is still a yarn version there? where that yarn version 1.15.2 is comming from?
    EduVencovsky
    @EduVencovsky
    Now I fixed the issue. The problem was that I didn't uninstalled npm before installing nvm, so that yarn was from the old npm.
    Sorry to bother guys, my mistake
    Corey Butler
    @coreybutler
    @EduVencovsky not a bother. I'm glad you figured it out!
    fati-pouk
    @fati-pouk
    Hi everyone
    JstnPwll
    @JstnPwll

    I totally removed NVM and Node, then got the latest NVM version and successfully installed the latest version of Node (14.8.0) plus npm. However, these versions that NVM downloaded seem non-functional.

    When I try to use node, I get this error:

    Program 'node.exe' failed to run: The specified executable is not a valid application for this OS platform

    When I try to run npm, I get Access is denied. and a popup saying the app cannot run on my computer.

    I saw someone in here had this issue a while back, and fixed it by explicitly installing a specific arch. I specified 64-bit when I installed node and still get this problem. Any tips?
    JstnPwll
    @JstnPwll
    (I'm on Windows 10)
    Corey Butler
    @coreybutler

    @JstnPwll there are a few reasons this can happen:

    1) Failure to run nvm use 14.8.0
    2) System permissions are blocking execution (run as admin).
    3) Corrupt download. Unfortunately, the error messages aren't as helpful as they should be with downloads. Sometimes there are false positives. If you can run node -v and see a version number, then you know it's something else.

    @/all - The NVM for Windows Github repository was accepted into the Github Discussions beta program today. The purpose of this Gitter channel was to facilitate discussion outside of the Github issues. However; Gitter as a chat platform kind of got squished by Slack, Teams, Discord, etc. Now that Github provides a viable place to carry on non-bug conversations, there is no longer a need for this channel. I will still pop on here occassionally over the next few weeks, but this is effectively notice that we're done using Gitter. All discussions can carry on at https://github.com/coreybutler/nvm-windows/discussions
    DrTeemo
    @DrTeemo
    On the github page for nvm-windows, the examples are using cmder. But when i try to use cmder to access nvm i get the message
    'nvm' is not recognized as an internal or external command, operable program or batch file.. Is there a guide on how i can fix that?
    3 replies
    Slađan Ristić
    @sladiri
    Hi, as far as I understand, all node versions share the same cache folder. I guess this is not an issue? Or should I set different cache folders?