Light-weight alternative to VSCode while still having language support. See inline docs in *.sublime-project file for Sublime project-level overrides.
CTRL + shift + p> "Install Package"; type "SublimeLinter"CTRL + shift + p> "Install Package"; type "SublimeLinter-eslint"CTRL + shift + p> "Install Package"; type "LSP"CTRL + shift + p> "Install Package"; type "LSP-typescript"
- NOTE: Will be overridden by local Sublime project settings to use project binary set in
*.sublime-project - Open "Preferences" > "Packages Settings" > "SublimeLinter" > "Settings"
- Set
linters.eslint.executableto the output of the following to ensure Sublime can use eslint:
which eslint- NOTE: Will be overridden by local Sublime project settings to use project binary set in
*.sublime-project - Open "Preferences" > "Packages Settings" > "LSP" > "Servers" > "LSP-typescript"
- Set
linters.eslint.executableto the output of the following to ensure Sublime can use eslint- Use
which nodeon Linux to figure out Node.js path - Windows default Node.js path is
C:\Program Files\nodejs\node.exe
- Use
This project employs a .sublime-project file that overrides the package settings/configs - configuring the language server (LSP), or linting (eslint) should be done here on a per-project basis.
IMPORTANT! Use the .sublime-project to launch the project or overrides will not be properly set.
For Windows support you will need to update the *.sublime-project paths for the the main Node.js executable for LSP, and npx for eslint; there are examples in the configuration file for a standard Node.js install on Windows at the location C:\Program Files\nodejs
- To debug linter/etc. errors use the console with `CTRL + ``
- Use
print('\n'*100)in the Sublime console to clear the output when testing