Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why does WebStorm's LiveEdit not work in Chrome?

Tags:

I am exploring WebStorm's trial version and would like to use the LiveEdit features.

I am not able to use the LiveEdit features after performing the following actions:

  1. Made sure that LiveEdit is turned on
  2. Installed the Chrome extension
  3. Restarted the browser after installing the extension (I still suspect it is not required)
  4. Run the HTML page in chrome

When I modify the HTML body, I don't see the changes reflected in Chrome.

I read on a forum that netty is not required.

Do we need it?

What else do I need to configure so that I can use the LiveEdit feature?

PS: I am using WebStorm 5.0.

like image 674
rajmalhotraml Avatar asked Dec 28 '12 12:12

rajmalhotraml


People also ask

How do I enable live server on WebStorm?

Activate and configure Live Edit in JavaScript On the Live Edit page that opens, select the Update application in Chrome on changes in checkbox. By default, WebStorm shows on-the-fly preview only for HTML and CSS code. To enable Live Edit in JavaScript, select the JavaScript, HTML and CSS option.

How do I debug WebStorm in Chrome?

If your application is running in the development mode on localhost , you can start debugging it from the built-in Terminal ( Alt+F12 ), from the Run tool window, or from the Debug tool window. Just hold Ctrl+Shift and click the URL at which the application is running. Set the breakpoints in your code.

Does WebStorm support HTML CSS?

The preview functionality relies on the built-in web server, which can only serve static content like HTML, JavaScript and CSS. To use it with PHP files, you need a local PHP interpreter specified for your project.

What is the difference between PHPStorm and WebStorm?

PHPStorm incorporates all the functionality that WebStorm comes equipped with (CSS, JavaScript HTML), PLUS full-fledged PHP support (and databases support).


2 Answers

Do you happen to have IntelliJ open by chance? The point is that the port, 63342, is 'seized' by another app (even if it has nothing to do with HTML debugging).

When the port is busy, LiveEdit tries the next one, 63343. If you right click the JB icon on Chrome, choose Options, increment the port by one, and press Apply, you will magically connect. I wish Jetbrains would have bothered to inform the user what is the port that they are currently attempting to use.

In my PC it happened when I had Mac on. Either one of the following worked: 1. Kill IntelliJ IDEA (that was also open) and try again 2. Increment the port by one as I mentioned above.

like image 75
Meymann Avatar answered Sep 29 '22 11:09

Meymann


I had to go to Run -> Debug (CTRL+F5 on Windows)

like image 37
Diego Vieira Avatar answered Sep 29 '22 12:09

Diego Vieira