I've got a ruby/cucumber project that I'm setting in a new windows machine. Everything seems to be in place (gemfile, rakefile, ruby 1.9.3 installed) but when I run 'bundle install' I get the message:
"jruby.exe" is not recognized as an internal or external command, operable programme or batch file.
Any idea where the problem can be? I don't know why it's even throwing that jruby error...
I've got exactly the same setup in another machine that doesn't have jruby installed either but 'bundle install' works fine there... :S
Cheers
The machine I was using was in a mess of environment variables and corrupt past installations of both, ruby and jruby.
Uninstalling everything and starting from scratch fixed the problem.
Related
I'm working on setting up the Suitecloud Development Framework in the NetSuite instance for my company. I've installed Node v16.13.0, npm 8.1.0, and suitecloud 1.3.1.
Running node -v, npm -v, etc. all works from cmd but will throw a not recognized error when I use the terminal in VSCode.
I can get my VSCode to identify node with
SET PATH=C:\Program Files\Nodejs;%PATH%
but this only fixes it for the session and still doesn't give me access to run anything from suitecloud.
I've checked my Environment Variables as per every other help section I've found for this issue but I have 'C:\Program Files\nodejs' in both my user PATH variable any my system PATH variable.
I've tried running VSCode as Admin on the off chance that would fix it, but that didn't solve anything either.
Thank you for your time, hopefully I'm overlooking something simple due to my inexperience with the terminal.
Leaving VSCode overnight and then rebooting seems to have fixed it. I can't explain why, but if you're encountering the same issue I recommend walking away and coming back to it after a long delay.
I have Node.js + NPM installed; I can run node -v in my console and get back the current version.
I have also tried using NVM Windows as a Node.js version manager and can run both node -v and npm -v there as well.
HOWEVER, when trying to use another framework like Gulp or Ionic or whatever, I keep getting the error:
'node' is not recognized as an internal or external command,
operable program or batch file.
node is obviously a cmdlet as I can run node -v.. but somehow my other frameworks are no longer able to find it.
Path is correct and everything looks good.
What am I missing here?
The program ConEmu for windows terminal management wasn't pulling or allowing programs to access the paths through subcalls or something it seems. I tested with CMD and Powershell respectively and both worked as expected.
I couldn't get ConEmu to seemingly pass these path to subroutines.. so I uninstalled it and found an alternative called Cmder that is built on ConEmu and it was able to pick them up just fine.
I don't know specifically if it was just a setting in ConEmu I couldn't find or if I needed to manually add these--but happy knowing Cmder just does it automatically.
I've seen bunch of 'tsc' is not recognized as an internal or external command issues here on StackOverflow but none of them could help me solve my problem.
I've installed typescript globally with:
npm install -g typescript
There are tsc and tsc.cmd files in C:\Users\<user_name>\AppData\Roaming\npm directory. So %AppData%\npm\tsc --version command works.
I've got C:\Users\<user_name>\AppData\Roaming\npm directory in my user's PATH.
More, when I run where tsc command in arbitrary directory, I get:
C:\Users\<user_name>\Desktop>where tsc
C:\Users\<user_name>\AppData\Roaming\npm\tsc
C:\Users\<user_name>\AppData\Roaming\npm\tsc.cmd
However, when I simply try to run tsc, I got:
C:\Users\<user_name>\Desktop>tsc
'tsc' is not recognized as an internal or external command,
operable program or batch file.
Exactly the same problem occurs with grunt and uglifyjs.
I managed to solve this problem.
C:\Users\<user_name>\AppData\Roaming\npm indeed was in user's PATH variable. I also have system variable called Path (yes, just first letter is uppercased) and there was no C:\Users\<user_name>\AppData\Roaming\npm in there.
When I added it to system's Path, it finally started to work.
Not sure that this is ok that two of my path variables have different names (in terms of cases). Also not sure that this situation led to problems.
Would be glad if someone could clarify this.
Try installing the linux console for windows the cygwin console., And run the command tsc from that console, I know it does not change much but sometimes I have solved many problems with that console.
https://www.cygwin.com/
So I was working through a tutorial to deploy my node app to a server. They had me npm install flightplan -g so I can use the 'fly' command. This all worked but for the fly command to work I needed to install rsync. I finally got rsync to work after changing my PATH. But now when I use to fly command I get "'fly' is not recognized as an internal or external command,
operable program or batch file."
I've tried changing the PATH hundreds of times to different things and I can't for the life of my get the fly command to work again. I've tried reinstalling flightplan globally a bunch of times. NOTHING IS WORKING.
Node JS NPM modules installed but command not recognized
This was the answer I was looking for.. I had the end of my path set to npm/fly and not just npm....
Regarding plugin for Coda 2. I am having some problems making it work. I have written a small test program in CoffeeScript, but when i try to run and/or compile I get the following error message:
All settings/env. variables should be set correctly:
Do you have any idea as to what that may cause this issue? I have installed node using homebrew, and then coffee script via npm. All the shell variables have been verified, and I am able to run node from the command line and write scripts there. Also, when i go to settings and click on "About", I get the following:
Hope you can help.
Thank you and best regards,
Thomas
In Terminal, run the command:
which coffee
For me, this gave:
/usr/local/bin/coffee
So in the CoffeeScript Plug-In Settings, I set PATH to:
/usr/local/bin
Then when I went to the About box, it showed the version of CoffeeScript that I have installed and the Run & Compile options then worked fine.