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

LSP-css

by sublimelsp ST3

CSS, SCSS, LESS support for Sublime's LSP plugin

Details

  • 1.2.0
    1.1.3
  • github.​com
  • github.​com
  • 6 days ago
  • 1 hour ago
  • 5 years ago

Installs

  • Total 9K
  • Win 3K
  • Mac 3K
  • Linux 3K
Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 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
Windows 4 4 5 5 8 6 1 3 2 4 7 4 3 5 4 1 6 3 2 1 4 4 5 6 6 2 2 3 2 2 2 5 1 7 3 2 4 7 3 4 1 5 3 4 1 4
Mac 5 5 0 2 4 4 1 1 1 5 2 0 4 4 5 0 1 3 4 4 6 5 4 1 1 0 3 2 6 4 2 2 2 0 3 5 4 5 2 3 0 3 1 1 4 2
Linux 3 4 0 3 5 2 3 2 4 3 2 2 2 3 5 7 3 3 3 5 5 3 4 1 5 2 3 4 1 4 2 1 4 1 3 4 3 2 8 3 1 2 1 4 6 4

Readme

Source
raw.​githubusercontent.​com

LSP-css

CSS, SCSS, LESS support for Sublime's LSP plugin provided through VS Code's CSS language server.

Installation

  • Install LSP and LSP-css from Package Control. If you use Sass install Sass. If you use Less install LESS.
  • Restart Sublime.

Configuration

There are some ways to configure the package and the language server.

  • From Preferences > Package Settings > LSP > Servers > LSP-css
  • From the command palette Preferences: LSP-css Settings

FAQs

  • I'm getting duplicate suggestions in the completion popup.

Sublime Text comes with a plugin that provides completions for the CSS and HTML syntaxes. This results in duplicate completions when using this package.

To disable ST's built-in completions for CSS syntax, for example: - open any CSS file - run Preferences: Settings - Syntax Specific from the Command Pallete - add "disable_default_completions": true in the view on the right

Repeat for other syntaxes that provide built-in completions. Same applies to third-party SASS package that provides SASS and SCSS support.

  • The server exited with status code 1.

It's probably that the node executable on your system is outdated. This plugin requires v14 as of version 1.0.9. If your OS is incapable of using Node v14 like Windows 7, you can