If I try to start debugging in Visual Studio Code, I get the following error:
No matter what launch.json I use I always get this error. Tried a lot of launch.json configuration. Don't know why it tries to load localhost:9876/debug.html when I set the url to localhost:8100.
My app is running on 8100 port. Debugger for Chrome is plugin is installed. How could I get rid of this error?
The fix was quite easy. For a long time I did not make a restart to my computer. After a computer restart the debug is working now.
Related
I downloaded the official Chrome nativeMessaging example to test it out.
To do this, I installed the app from chrome://extensions, by choosing Load Unpacked. No problems so far.
I then installed the host. I'm using Windows 7, so I ran install_host.bat, which claimed that "The operation completed successfully." However, when I go to chrome://apps/ and click the Connect button, I get this error:
Failed to connect: Native host has exited.
Is there some reason this would happen? Restarting Chrome did not fix the issue, nor did uninstalling and then reinstalling the host program.
(I noticed that native-messaging-example-host.bat requires Python 2, so I modified it to run Python 2 explicitly. If I run native-messaging-example-host.bat from the command line, it pops up a little example program of its own with a GUI and seems to work correctly.)
Turns out I was using a non-standard character in the path leading to the host executable. This wouldn't be a problem for any other program, but Chrome's native messaging API doesn't like it, I guess.
By the way, the documentation on setting up this example is near-nonexistent, but this stack overflow link has some useful info: Chrome Extension NativeMessaging 'connectNative' undefined
I have a localhost website created with ember which is just working fine.
I want to use Lighthouse to get some metrics about the performance over time. Of course I want this to be in Chrome and headless. I installed Lighthouse using NPM and run the following command:
lighthouse http://localhost:4200 -chrome-flags='--headless'
When running above, I got the following error resulting in a question mark as a performance metric:
Chrome didn't collect any screenshots during the page load. Please make sure there is content visible on the page, and then try re-running Lighthouse. (SPEEDINDEX_OF_ZERO)
I tried running the dist folder of ember with the http-server package, but no differences in the result. The same error occurs.
When I run the test against google.com or against a website in our test environment I get a result back and not the error. When a colleague is running it on his local machine, no error occurs. Only difference we can find is he is running win8.1 and my machine is win10.
When I run Chrome without the headless flagg I also get a result, but I need it to work headless.
I'm using all the latest versions of Lighthouse, Chrome, Windows10, node. Also tried Chromium but no differences.
Hopefully someone got an idea
After a week I tried again, still the same error. Now I tried again and it works. Nothing changed to my codebase and all apps, packs and so on are also the same version which I can see.
I don't know what fixed the issue, but it works now. Case closed.
I have inherited a JMeter performance testing script. There is a chromedriver section and an HTTPSampler section. The httpsampler section works fine. The chromedriver section runs into a problem. When I run it chrome pops up like this:
It does not move forward with any of the steps in the plan after that. Up until recently I've also been seeing the error
Error communicating with the remote browser. It may have died.
I am not seeing this now, so I don't know if it's just a difference in how the test is running or what.
The person I inherited this from was running it on a mac and did not get any of these problems. I saw it run with no errors at the same time I was getting them.
One solution I found was to add the --test-type flag to chromedriver. Unfortunately I cannot find a way to add that argument when running it through JMeter. I've tried adding both --test-type and -test-type to the end of the path to chromedriver.exe, but that did not work.
Does anyone have a solution for this?
The error might be due to conflict in chrome driver version. Please install the latest version of ChromeDriver from this link.
Latest version of Chrome Driver supports the browser version v56-58.
I just installed and repaired my VS2013 to build Native Cordova App. I have also installed the latest version of NodeJS but whenever I am trying to build the Application It gives me an error. I am uploading an image for more details on error as I believe image provide more info than text.
Posting error details if error is not clear in an image
Cannot find module 'q'.
The command ""C:\Users\nnnc\AppData\Roaming\npm\node_modules\vs-mda\vs-cli" prepare --platform Android --configuration Debug --projectDir . --projectName "BlankCordovaApp1" --language "en-US"" exited with code 8. C:\Users\nnnc\AppData\Roaming\npm\node_modules\vs-mda-targets\Microsoft.MDA.targets
I have advanced a little bit more but having hard time to run the application I have to manually installed all the required module. but now whenever I am running my project I get an error of web page is not available. please look at the attached image again.
I found that running npm install from within /vs-mda/ solved all my problems.
found the fix and that Involved manually loading packages like q via node js and in the end the fix for web page is not available was that ripple has changed and now we should not add it as an extension via chrome. it should be done via node js as well as below
npm install ripple -g
but before doing that delete it from chrome if you have got it otherwise just run the command.
Regards
Don't know what happened, but it just hangs on "Type Space loading (4%)" and that's it. I tried to solve problem with -clean option and with deleting .history and eclipse resources folder under plugins. I also tried with new workspace and it's still the same.
Before that I installed JVET. Don't know if it's connected with that.
Yes, it's because of VJET, see https://www.ebayopensource.org/jira/browse/VJET-57
To me it happened on a fresh installation of Eclipse IDE for JavaScript Web Developers.
Just leave it for about half an hour and it should finish successfully.
May i ask why did you install VJET? If as me to be able to debug node.js you might wanna try https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger