ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Live​Server

by molnarmark ST3

🌍️ Launch a Development Server directly from Sublime Text

Details

Installs

  • Total 64K
  • Win 48K
  • Mac 6K
  • Linux 10K
Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16
Windows 6 8 9 2 9 10 4 3 6 10 9 9 10 9 4 8 4 6 11 7 5 11 10 7 12 6 6 3 3 7 9 12 11 9 8 12 6 12 12 13 7 8 13 6 5 3
Mac 0 1 1 3 5 0 0 3 3 5 3 3 4 1 0 0 0 2 1 3 2 1 2 0 0 3 2 4 1 0 1 1 0 0 1 2 1 3 3 3 1 2 4 0 4 1
Linux 1 3 3 4 2 3 4 0 3 1 3 2 3 5 0 2 3 1 4 3 5 6 1 2 2 7 2 1 4 1 2 3 1 1 3 5 4 0 1 3 2 6 5 1 2 3

Readme

Source
raw.​githubusercontent.​com

Launch a Development Server directly from Sublime Text!

📋 Introduction

This package integrates the Live Server Node package, giving the ability to launch a local development server to serve content directly from Sublime Text.

💡 About Live Server:

Live Server is Node.js tool that spins up a local development server in the given directory.

It features live browser reloading, which simply means that your browser will automatically refresh the page when any change is made to your HTML & CSS files.

Useful for static sites, SPAs, and general HTML/CSS fiddling.

❗Prerequisites

You need the following software installed to use Live Server.

To install Live Server globally using npm, run:

npm install -g live-server

To install Live Server globally using Yarn, run:

yarn global add live-server

🌀 Installation

Package Control

This package is available in Package Control under the name LiveServer.

As a Repository

❓ Usage

This package exposes 3 commands that can be used directly via the Command Palette, or bound to keys. These are:

Live Server: Start

  • Maps to live_server_start

Live Server: Stop

  • Maps to live_server_stop

Live Server: Open In Browser

  • Maps to live_server_open_in_browser

Status bar messages with indicator emojis are implemented into the package, displaying information in cases such as:

  • 🎉 Live Server running
  • ❌ Live Server stopped
  • ✔️ Live Server status

When the development server is running, a status message will be shown in the status bar indicating that the server is running. This is shared across all views in the opened instance.

🔨 Settings

To change your settings, bring up the Command Palette and select: Preferences: Live Server Settings

The default settings for linux are the following:

// Note: These are just mappings to https://github.com/tapio/live-server#usage-from-command-line
{
  "node_executable_path": "/usr/bin/node",
  "global_node_modules_path": "/usr/local/lib/node_modules",
  "port": 8080,
  "address": "localhost",
  "cors": true,
  "browser": "default",
  "nobrowser": false,
  "wait": 100
}

node_executable_path

  • Path to the Node runtime executable. You can run whereis node in your terminal to find this.
    • In Windows Command Prompt, run where node
  • ##### default value: /usr/bin/node

global_node_modules_path

  • Path to the default node_modules directory. You can run npm root -g** or **yarn global bin in your terminal to find this.
  • ##### default value: /usr/local/lib/node_modules

port

  • The default port for the server.
  • ##### default: 8080

address

  • Host address. This should always be either localhost or 127.0.0.1.
  • ##### default: localhost

cors

  • Enables CORS for any origin.
  • ##### default: true

browser

  • Specifies which browser to use.

  • Valid values are:

    • default
    • google-chrome
    • firefox
  • default: default

nobrowser

  • By setting this to true, the browser will not open the server by default
  • ##### default: false

wait

  • Wait this amount of milliseconds before reloading the page after a change
  • ##### default: 100

🔖 Credits