Learn You The Node.js For Much Win! An intro to Node.js via a set of self-guided workshops.
Learn JavaScript by adventuring around in the terminal.
Bumps http-cache-semantics from 4.1.0 to 4.1.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.
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:
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):
What did I do wrong? Why doesn't javascripting start in my case like in the tutorials I've seen on the net?
Thanks