LSP-file-watcher-chokidar
Chokidar-based file watcher implementation for LSP
Details
Installs
- Total 8K
- Win 3K
- Mac 2K
- Linux 3K
| Jan 21 | Jan 20 | Jan 19 | Jan 18 | Jan 17 | Jan 16 | Jan 15 | Jan 14 | Jan 13 | Jan 12 | Jan 11 | Jan 10 | Jan 9 | Jan 8 | Jan 7 | Jan 6 | Jan 5 | Jan 4 | Jan 3 | Jan 2 | Jan 1 | Dec 31 | Dec 30 | Dec 29 | Dec 28 | Dec 27 | Dec 26 | Dec 25 | Dec 24 | Dec 23 | Dec 22 | Dec 21 | Dec 20 | Dec 19 | Dec 18 | Dec 17 | Dec 16 | Dec 15 | Dec 14 | Dec 13 | Dec 12 | Dec 11 | Dec 10 | Dec 9 | Dec 8 | Dec 7 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 3 | 5 | 2 | 1 | 3 | 4 | 6 | 4 | 5 | 0 | 4 | 5 | 1 | 6 | 2 | 1 | 3 | 3 | 2 | 0 | 4 | 7 | 0 | 3 | 5 | 4 | 3 | 2 | 4 | 1 | 1 | 6 | 1 | 6 | 3 | 5 | 3 | 2 | 3 | 3 | 4 | 4 | 1 | 4 | 5 |
| Mac | 1 | 1 | 1 | 2 | 1 | 4 | 2 | 2 | 3 | 0 | 1 | 2 | 5 | 3 | 5 | 0 | 1 | 1 | 3 | 5 | 1 | 6 | 2 | 4 | 2 | 3 | 1 | 3 | 2 | 5 | 1 | 4 | 2 | 7 | 2 | 5 | 1 | 4 | 4 | 4 | 4 | 1 | 0 | 4 | 5 | 5 |
| Linux | 0 | 2 | 1 | 0 | 2 | 2 | 0 | 0 | 1 | 1 | 1 | 5 | 2 | 1 | 1 | 4 | 3 | 1 | 4 | 2 | 4 | 4 | 2 | 0 | 4 | 3 | 5 | 1 | 3 | 8 | 3 | 2 | 3 | 1 | 0 | 4 | 2 | 7 | 6 | 0 | 3 | 3 | 0 | 2 | 1 | 2 |
Readme
- Source
- raw.githubusercontent.com
LSP-file-watcher-chokidar
A non-native file watcher implementation for LSP that enables support for the workspace/didChangeWatchedFiles LSP notification.
Installation
- Install
LSP-file-watcher-chokidarfrom Package Control - Restart Sublime.
Usage
Having this package installed alongside LSP enables the workspace.didChangeWatchedFiles capability and support for the workspace/didChangeWatchedFiles notification. The servers can also dynamically register file watchers.
For LSP-* packages that are within the sublimelsp organization it should be enough to just install this package and file watching should work without any extra configuration.
In other cases, it might “just work” (if the server registers watchers dynamically) or it might require manual configuration using the the file_watcher object on the Client configuration object.
file_watcher object properties:
| Name | Optional | Description |
|---|---|---|
| patterns | No | An array of glob patterns defining which files within the workspace should be watched. The patterns are relative to the workspace root. Example: ["{**/*.js,**/*.ts,**/*.json}"]. See also supported pattern syntax. |
| events | Yes | An array with the type of events to watch. Default: ["create", "change", "delete"] (all supported types). |
| ignores | Yes | An array of glob exclude patterns. By default this includes patterns from Sublime Text's folder_exclude_patterns and file_exclude_patterns settings and additionally the '**/node_modules/**' pattern. When overriding this option the defaults are not included anymore. |
Implementation
Registering a watcher creates a new Node process behind the scenes. The current implementation creates at most one process for any number of registrations (even through different language servers).
The reason that this is implemented as a separate package, and not natively within the LSP package, is that this relies on a separate process that does the file watching and for the built-in implementation we would like to use a native API provided by Sublime Text that it doesn't provide at the moment. See the LSP issue #892 for supporting it natively within the LSP package.