Unable to use live server

[KingDamo17]

Sublime text shows the live server command palette but does not do anything if I hit start or stop.

I am on mac and new to programming, so I could not clean up the npm audit. If I even need to.

[molnarmark]

Did you set up the plugin according to the documentation? https://github.com/molnarmark/sublime-live-server#-settings

[monavari-lebrecht]

Tried it by myself, but what do you mean by setting it up. The default settings should work out of the box, shouldnt they?

The problem is, that it doesnt show any update, after doing the start command. And when you try to run Open Live server in Browser, it says, Live server isnt running

[molnarmark]

The default settings indeed work, but only on Linux. Any other OS, you need to change the settings.

[fawadta]

Did you set up the plugin according to the documentation? https://github.com/molnarmark/sublime-live-server#-settings

yea i did. but on live server start and stop, it don't do anything but on live server open in browser it displays: live server isnt running. nothing to open
I dont know what to do...

[guillermodelrio]

for Mac users:

{
  "node_executable_path": "/usr/local/bin/node",
  "global_node_modules_path": "/usr/local/lib/node_modules",
}

Also, make sure you have saved first your working file before attempting to launch Live Server from the command palette!

[haighd22]

for Mac users:

{
  "node_executable_path": "/usr/local/bin/node",
  "global_node_modules_path": "/usr/local/lib/node_modules",
}

Also, make sure you have saved first your working file before attempting to launch Live Server from the command palette!

is it always "node_executable_path": "/usr/local/bin/node",? I ran whereis node as per the readme and got a path of "/usr/bin/node /usr/include/node /usr/share/man/man1/node.1.gz". Neither seems to work as the node_executable_path within settings and I get the same issue as the OP.

Any help much appreciated.

[molnarmark]

@kyle-wendling Great, so use that instead.

This package is just a wrapper around an npm library. I don't control anything when it comes to that particular library, as I didn't write it. This package currently has ~58.000 installs, most people with issues were able to solve them, and this is the same package that powers VSCode's version of this package. If you really want to complain, this is where you need to go. It looks like you really felt the need to complain before checking out what the package actually does.

[molnarmark]

@frostphex The comment was directed at the person I tagged (User "kyle-wendling", possibly trolling or overly entitled), who since then deleted the comment. :)

He complained that he made a package in 10 minutes which was in every way better than this one, so I told him to complain about the original npm package at its repository, as this plugin is just a wrapper around it.

It's not directed at people who come here with decent mannerisms asking for guideance about the package. :)

[molnarmark]

@frostphex Of course, its understandable.

The "Open in browser" feature (if you mean the one where you right click on the file in the sidebar) is not part of this plugin. That is provided by a different plugin (maybe this) or built into Sublime Text by default, I honestly don't remember.

If you launch the server, you should be able to access the files in the browser by navigating to localhost:8080, or whatever port you've set up in the settings.

Yes, some people had problems, most (as far as I know, ~59.000 installs so far) were able to get things going.
It's just really hard to help others if you don't experience/can't reproduce the issue they are having.

[molnarmark]

@frostphex A lot have moved to VSCode, yes, that is one of the reasons.

When it comes to this package, it's using this NPM package underneath, which haven't received updates in a while either, so there are no new features to implement into this plugin.

[rmpasswd]

For windows, i had to run these. also opened a pull req.
note that in the file paths, backslash has to escaped with another backslash