I was trying to install "qunit" using Windows command Prompt by executing the command
"npm i qunit".
On executing , it loads something and then it does not show anything . I have to press Ctrl+C twice to stop whatever this command is executing in the background.
Because of this "qunit" is not getting installed properly.
How should i resolve this problem ?
Related
npx npm run cypress --headless running this code in my project is still opening up a google chrome user, requiring UI to keep it going
no matter what I try, even uninstalling and reinstalling cypress doesn't fix the issue
The correct way is:
cypress run
Actually by default this command is executed in headless mode, that's why it's not necessary to write --headless. And if you want to run it in headed mode, then:
cypress run --headed
I want to run appium program and see appium process running in terminal automatically on startup
I have created a simple bash script to run the appium command using gnome-terminal.
appium.sh
#!/bin/sh
gnome-terminal -- appium
and when I run the command by terminal ./appium.sh it works.
(Use `node --trace-deprecation ...` to show where the warning was created)
[Appium] Welcome to Appium v1.21.0
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
but when I put in sudo nano /etc/xdg/lxsession/LXDE-pi/autostart to run the program automatically at startup.
#lxpanel --profile LXDE-pi
#pcmanfm --desktop --profile LXDE-pi
#lxterminal -e bash /home/pi/appium.sh
#xscreensaver -no-splash
gnome-terminal opens successfully, but the appium command fails to run.
There was an error creating the child process for this terminal
Failed to execute child process “appium” (No such file or directory)
Is there something wrong ? please help
When I run npm commands on my Windows 10 machine, new processes seem to spawn in new windows.
On my (Mac-using) colleagues machines, I see that these commands run in the same terminal window from which they were called. This is the behaviour I'd expect and is much more useful - it's really hard, for instance, to see my test results in the split second between them finishing and the terminal window being closed!
As an example, our packages.json has a script to run jest:
scripts": {
"test": "jest"
}
When I run npm run test, the following gets written to the current terminal:
$ npm run test
> #headuplabs/mobile#0.0.1 test C:\Users\TomWright\Documents\Repos\HeadUp.Mobile
> jest
But the actual execution of jest then gets started in a newly created window:
I'm using "git bash" as my default integrated terminal in VS Code, but I'm able to replicate this using cmd.exe and outside VS Code (i.e. by running git bash or cmd standalone).
I presume that my npm installation is improperly configured, but my Google search haven't yielded any answers.
Does anyone know what I'd need to do to make npm processes run in the same terminal window?
As mentioned in "how to set shell for npm run-scripts in windows", you might want configure the shell in npm itself:
npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe"
That would avoid the default setting, which can trigger a new shell window.
I am facing some weird issue. Before updating SlimerJS and casperJS every script were working fine but since from yesterday i am not able to run the scripts. when i run this below command to run the script
sudo xvfb-run -a casperjs test --engine=slimerjs testsuite/testing_part1.js --username=user --password=pwd --url=url_of_the_site
every scripts are getting failed
has anybody know what/why this error i am getting?
Currently i am using SlimerJS=SlimerJS 0.9.6 and CasperJS=1.1.0-beta3
Add http:// to your URL like this:http://URL.It will work
I'm having problems getting Docpad to run on Windows.
I did the following.
Installed the latest version of Node
"NPM Install Docpad"
Then typed "docpad run" in an empty directory
I got an error message that said 'docpad' is not recognized as an internal or external command,
operable program or batch file.
Maybe I'm missing a step somewhere? I've also tried submitting the command to the node command prompt, and have also checked the troubleshooting guide and done a general google search.
Unless you installed an NPM module with the -g option (which is not indicated in the docpad web site so I suspect you didn't) the module won't be available on your PATH.
You can still run it by indicating the full path, for example run the following from the folder where you ran the npm install command:
node_modules\.bin\docpad.cmd
I had this same problem and a restart didn't help me.
What worked for me was installing via the 'nodejs command prompt' rather than the standard windows one.
I ran npm install -g docpad then navigated to my empty folder and ran docpad run and it worked straight away (after 1 hour messing around with the windows command prompt).