On my Windows PC I have the latest version of node 6.9.1 which has V8 inspector built in. When I use the --inspect flag to run an app.js file and go to the "chrome-devtools" URL to attach the Debugger, everything works fine (I can set breakpoints and step through the code) but console.log code doesn't print to the chrome console. I already checked the console filter, it is set to ALL. It prints to the console window where I ran the app, just not to Chrome.
I have Windows Server 2008 R2. I dont have this issue on my macbook, it logs to the chrome console fine. I was hoping someone could check if they have it working on their Windows computer or if anybody else has run into this issue. Maybe its just a Server 2008 R2 issue?
It is very easy to test. Just create an app.js file with 1 line "console.log('test')", open command prompt or git Bash or whatever in the folder and type:
node --inspect --debug-brk app.js
It will give you a chrome-devtools URL. Go to this URL in chrome and you will see your app. The script execution will be stopped (due to the -brk flag) so you will have to resume it. If you have the same issue as me, you will notice that when you resume it, nothing will be logged to console.
I had the same problem. ( Node 6.11.0, V8 Inspector and no console)
I've updated Node.js to version 8.9.0 for Windows
I've downloaded the msi file here
Now everything it's OK.
Related
I'm having issues with vs code (using it on my iPad Through a raspberry-Pi-4) with node and node.js and I can’t execute my code or even open the terminal
I cannot open Appium inspector on Linux Ubuntu.
In the same folder I have 3 files:
Appium-Inspector-linux-2022.2.1.AppImage /
Appium-Server-GUI-linux-1.22.2.AppImage /
latest-linux.yml
When I open the Appium-Server-GUI-linux-1.22.2.AppImage file, start the server e click on the button to open Appium Ispector, it open a web page.
to fix this, it was necessary:
1: Start Appium Server
I did this, executing Appium-Server-GUI-linux-1.22.2.AppImage file.
2: Start Appium Inspector through of file Appium-Inspector-linux-2022.2.1.AppImage
3: Create the capabilities
After that, the Appium Inspector still don't open throught on Appium Server button, but it make it open and you can use.
Since the release of Appium v1.22 they have changed how the Appium Inspector works. I refer you to their official documentation on GitHub https://github.com/appium/appium-inspector, citing:
Appium Inspector is released in two formats:
As a desktop app for macOS, Windows, and Linux. You can get the most
recent published version of this app at the Releases section of this
repo. Simply grab the appropriate version for your OS and follow
standard installation procedures (but see the note below for macOS).
As a web application, hosted by Appium Pro. (It's currently a known
issue that the web version does not work on Safari). Please make sure
to read the note below on CORS as well.
If you like to work the old way, download Appium Desktop v1.21 or below.
install latest appium-inspector
open appium-inspector and insert "/wd/hub" in Remote Path
I'm learning react, and Installed live-server via npm globally. Each time i try to serve the directory (live-server public), i get a windows error saying - "this app can't run on your pc"
I am using windows 8.1
I found the problem, the problem was that live-server was trying to render my app using a browser but the default chrome browser was having issues so it kept popping that error.
The solution was just to set Firefox as my default browser from the control panel. Control Panel>default programs
I have an app that I made with yeoman, grunt an angular JS (typical setup - image included below). I'm trying to debug my project with spyjs (or even regular javascript debugging) but I can't seem to get it working when I run "grunt serve" - the file that's loaded from WebStorm clearly isn't going through the grunt server (but localhost:63343 instead). Any ideas how I could configure things properly to get debugging to work?
Here's my SpyJS configuration:
I've also tried localhost:9000 for the URL to trace (which is the port that grunt serve runs on), and I've tried using another node interpreter.
You need using the server your client code runs on (localhost:3000) and not WebStorm built-in webserver to debug your Angular application served by Grunt. See Debugging grunt with Intellij for some hints
Note: haven't tried this with spyjs - only with a regular debugger
You need to upgrade to Webstorm 9. As per spy-js
Node.js tracing is now supported in WebStorm 9 EAP, including multi process and node cluster tracing support.
Then instead of using Spy-js profile, use Spy-js for Node.js profile.
This screenshot is from Webstorm 9 RC.
I am using too the Yeoman generator (AngularJs + grunt), and I am debugging the application using the JavaScript Debug configuration like this:
(source: ignaciosuay.com)
Have a look to this post about how to debug angularJS with Intellij (It should work too for web storm)
Can anyone help me please onto this issue. I have just installed webstorm 8 and trying to create a Node.js-express application and getting following error. It pops a node window but shuts it off within milliseconds. Also if i am trying to create a node.js project manaully, i cannot debug node.js it says "Process finished with exit code 0" . Please note if i try to run node from command prompt it is running fine. I am using windows 8
Try choosing node.exe instead of nodevars.bat as Node executable
Try to update your ide. Its working on my case