workshopper / javascripting

Learn JavaScript by adventuring around in the terminal.
http://nodeschool.io
MIT License
2.86k stars 1.05k forks source link

Trying to run javascripting #351

Open Dnalab01 opened 1 year ago

Dnalab01 commented 1 year ago

Describe the bug

Hi, I'm a newbie and it's my first time trying Javascripting.

I followed the instructions and after installing node.js, I opened CMD as administrator, on Windows 11. I ran the command npm install -g javascripting, and next i wrote javascripting, but nothing happens. Just an error: "javascripting" is not recognized as an internal or external command, an executable program or batch file.

To Reproduce Steps to reproduce the behavior:

  1. Install node.js'
  2. Open Comand Prompt on Windows 11 as Administrator
  3. i see that in my prompt: C:\Windows\System32>
  4. Type: npm install -g javascripting
  5. wait npm finish installation, installation is ok
  6. Type: javascripting (something like that: C:\Windows\System32>javascripting)
  7. error

Expected behavior Through the tutorials and videos I've watched, the javascripting program launches on the CMD.

So I did this

The npm install had no error, but I couldn't read the installation directory (too fast). I tried to figure out in which directory npm was actually installing javascripting. After some tries, I found javascripting in this directory:

C:\Windows\System32\node_modules\.bin From here, you can also double click on javascripting.cmd.

I wrote this in command prompt

_cd nodemodules

C:\Windows\System32\node_modules>

cd .bin

C:\Windows\System32\node_modules\.bin>

javascripting

javascripting starts It works!

Execution environment (please complete the following information):

What did I do wrong? Why doesn't javascripting start in my case like in the tutorials I've seen online?

Thanks

aashmanVerma commented 1 year ago

@Dnalab01 I guess you have to set enviroment variables in order to set the path so that command can be available outside the folder

ledsun commented 1 year ago

If possible, I suggest using Windows Subsystem for Linux.

dhanmeetsingh commented 1 year ago

The issue seems to be caused by a missing environment variable that points to the directory where npm installs global packages. This variable is typically named "PATH" and should include the path to the ".bin" directory of the npm global package installation.

When you run the "npm install -g" command, it installs the package globally on your system. However, if the PATH environment variable is not set correctly, your command prompt may not be able to find the executable files of the globally installed packages.

In your case, since you were unable to launch the "javascripting" command from the command prompt, it appears that the ".bin" directory of the npm global package installation was not included in the PATH environment variable.

To fix this issue, you can add the path to the ".bin" directory of the npm global package installation to your system's PATH environment variable. You can do this by running the following command in your command prompt:

setx PATH "%PATH%;C:\Windows\System32\node_modules\.bin" This command adds the path to the ".bin" directory of the npm global package installation to the existing PATH environment variable. After running this command, you should be able to launch the "javascripting" command from the command prompt without any issues.