workshopper / workshopper/javascripting

Trying to run javascripting

Open
#351 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.9k
Forks
1k
Avg merge
14h 47m
Merged PRs (30d)
1

Description

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 node_modules

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):

  • OS: Windows 11
  • Version 22621.1105
  • Node Version v19.4.0
  • NPM 9.3.1

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

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the installation from a Windows 11 Command Prompt using Node v19.4.0 and npm 9.3.1, starting with the reported npm install -g javascripting command and the javascripting entry point. Check how the global executable location is exposed to PATH and compare it with the working node_modules\\.bin invocation. Done means identifying whether this is a package or environment issue and documenting or testing a reproducible resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.