ansible-language-server
typescript-language-server
Our great sponsors
ansible-language-server | typescript-language-server | |
---|---|---|
13 | 53 | |
250 | 1,699 | |
- | 4.1% | |
8.0 | 8.7 | |
about 1 month ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ansible-language-server
-
The Bullhorn #108 (Ansible Newsletter)
Version 1.1.0 The Ansible Language Server (ALS) underwent a substantial upgrade. ALS v1.1.0 has adopted the new YAML 2.x package and successfully updated its code base accordingly. This significant development brings enhanced capabilities in terms of YAML diagnostics and strengthened security measures. Another crucial feature addition was the completion for variables declared inside a playbook. Full list of change-logs here.
-
The Bullhorn #93 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
[Ansible] Visual Studio Code et l’extension Redhat Ansible (quelqu’un peut-il le faire fonctionner) ?
Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :
-
Anyone here have success with Ansible syntax highlightning lsp?
You are conflating multiple functions. I have used the ansible language server 1 with decent success in both 0.7 and 0.8. It provides autocompletion of modules and diagnostics from ansible-lint, but does nothing to address syntax highlighting. Your project should have either an ansible.cfg or .ansible-lint at your project’s top level and your yaml files should be of filetype yaml.ansible. If you run :LspInfo it should display ansiblels as active.
-
LSP configuration
I'm looking to use a language (Ansible flavored YAML) that does have an LSP implementation, but is not supported by tree-sitter.
- How to properly set up LSP ansible language server in emacs, for proper ansible playbook editing support?
-
A new version of vscode ansible extension is out
Does the standalone usage help?
-
The Bullhorn #45 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
Red Hat Ansibe Extension for VSCode
Additionally, I found that the entire extension stopped working because in the past, easy-install had added a .egg file to my python path. I submitted a fix and it was accepted, but I'm not sure if the fixed language server is part of the current extension version. Might be worth checking for files like that in the paths listed in sys.path.
-
Visual Studio Code and the Redhat Ansible extension (can anyone get it to work) ?
I think we found the bug as https://github.com/ansible/ansible-language-server/issues/117
typescript-language-server
- Helix - Front-End Power
-
What is JSDoc and why you may not need typescript for your next project?
Besides the features TypeScript itself proposed, the most important thing it brought to the community was the ability to create cool features around this compiler that enhance the developer experience and productivity. Tools like tsserver, pretty ts errors, and many others are actively improving the ecosystem for both JavaScript and TypeScript writers.
-
A guide on Neovim's LSP client
Sometimes a language server can support multiple filetypes. An example of this is tsserver, the language server for javascript and typescript. In this case a filetype plugin can still work but there is an easier way to go about it.
-
Suspense your federated component with caution
in this way the ts server can detect and parse the component from the microfronent, thanks to monorepos!
-
Let's write an Emacs treesitter major mode
That was interesting, thanks for pointing it out
I was tremendously sad to see that the Typescript Language Server wasn't owned by Microsoft <https://microsoft.github.io/language-server-protocol/impleme...>, since if there was any sanity in the world a spec bump would travel with a reference implementation showing how they envision such a thing being used
But, I found that the Typescript Language Server that they did list does indeed have a semantic-tokens module in it, although it's much shorter than I would have expected from reading that section in the spec: https://github.com/typescript-language-server/typescript-lan...
-
How do I select which LSP is currently running?
I would like to use svelte language server when working on +page.server.ts files and not the typescript language server.
-
Formatting on save not working
[[language]] name = "python" roots = ["pyproject.toml"] formatter = { command = "black", args = ["--quiet", "-"] } language-server = { command = "pyright-langserver", args = ["--stdio"] } config = {} auto-format = true [[language]] name = "rust" auto-format = true # [[language]] # name = "typescript" # auto-format = true # formatter = { command = "prettier", args = ["--parser", "typescript"]} # # pass format options according to https://github.com/typescript-language-server/typescript-language-server#workspacedidchangeconfiguration omitting the "[language].format." prefix. # config = { format = { "semicolons" = "insert", "insertSpaceBeforeFunctionParenthesis" = true } } [[language]] name = "tsx" formatter = { command = 'prettier', args = ["--parser", "typescript"] } auto-format = true [[language]] name = "javascript" auto-format = true formatter = { command = 'npx', args = ["prettier", "--config", ".prettierrc", "--parser", "javascript"] } # formatter = { command = "prettier", args = ["--parser", "javascript"]} [[language]] name = "css" formatter = { command = 'prettier', args = ["--parser", "css"] } [[language]] name = "markdown" # https://github.com/executablebooks/mdformat formatter = { command = "mdformat", args = ["-"] } [[language]] name = "json" formatter = { command = "prettier", args = ["--parser", "json"] } [[language]] name = "toml" auto-format = true # https://github.com/bd82/toml-tools/tree/master/packages/prettier-plugin-toml formatter = { command = "prettier", args = ["--parser", "toml"] } [[language]] name = "yaml" indent = { tab-width = 2, unit = " " } formatter = { command = "prettier", args = ["--parser", "yaml"] } [[language]] name = "astro" scope = "source.astro" injection-regex = "astro" file-types = ["astro"] roots = ["package.json", "astro.config.mjs"] language-server = { command = "astro-ls", args = ["--stdio"] } config = { "typescript" = { serverPath = "/Users/matteostara/.nvm/versions/node/v18.16.0/bin/typescript-language-server" }, "environment" = "node" }
-
Struggling with javascript completion with LSP
Depending on the language server version, you may be running into https://github.com/typescript-language-server/typescript-language-server/issues/631. I temporarily fixed it for me by simply sticking with an old enough server build, though judging by the latest typescript-language-server commits a very recent build from master should also work
-
There's another typescript LSP that wraps the official VSCode typescript extension and has almost the same features - vtsls
Before, I was using typescript-language-server as it is LSP compliant but it was slow and lacks the features of what VSCode's implementation has, like extracting functions, constants, types into interfaces or alias and single imports. Auto-completion was also not very predictive as sometimes it works and sometimes it doesn't. For instance, I was having trouble getting it to auto-complete common attributes like className or href in JSX projects. It could be that I may be doing something wrong but didn't find any solution on how to get it properly working.
-
What could cause my LSP to be so slow and sluggish? Takes anywhere from 1 to 8 seconds to show auto-completion results and hide/ unhide errors.
Then this is highly likely issue of typescript-language-server. You might consider opening an issue for it.
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
deno - A modern runtime for JavaScript and TypeScript.
nvim-lspconfig - Quickstart configs for Nvim LSP
jupyterlab-lsp - Coding assistance for JupyterLab (code navigation + hover suggestions + linters + autocompletion + rename) using Language Server Protocol
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
nvim-lsp-ts-utils - Utilities to improve the TypeScript development experience for Neovim's built-in LSP client.
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
nvim-lspinstall - Provides the missing :LspInstall for nvim-lspconfig
ansible-navigator - A text-based user interface (TUI) for Ansible.
TypeScript - IO wrapper around TypeScript language services, allowing for easy consumption by editor plugins