Ansible Language Server (generic lsp implementation for Neovim)

Greetings. I’ve been a happy Ansible content developer for over a decade and have used many different development environments, IDEs, and text editors over the years. I’ve been back on the vi/vim/neovim path for the past couple of years and have it setup to support numerous languages and, for those languages, have several features such as syntax highlighting, completions, linting, etc.

I patted myself on the back when I got ansiblels working via the Mason external tool manager for Neovim and was thrilled to have Ansible-aware completions, goto definition, etc.

As I look at it today, I see that the actual LSP behind the scenes is a Node module hosted on npmjs.com that is nearing 2 years old (https://www.npmjs.com/package/@ansible/ansible-language-server?activeTab=versions).

I realize that this was likely based on the now-archived ansible-language-server project (GitHub - ansible/ansible-language-server: 🚧 Ansible Language Server codebase is now included in vscode-ansible repository) and that the ALS project is now encapsulated in the vscode-ansible project (GitHub - ansible/vscode-ansible: Ansible IDE extension: auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.).

Is anyone else using Neovim and have a modern Ansible-aware based LSP integrated? Where are the artifacts published/available?

The older ansiblels v1.2.3 from npmjs.com still works (rather well actually), but I’d like to stay up-to-date as much as practical and take advantage of new features.

Thanks, and happy automating.

Figures the first reply would be from myself in about an hour, but I did eventually stumble upon a GH issue here (Release ALS as a standalone pkg on npmjs.com · Issue #1543 · ansible/vscode-ansible · GitHub). And now this post and GH issue are doubly linked.