vscode-antlers-language-server
vscode-antlers-language-server copied to clipboard
Plugin not working on insiders build
Describe the bug
I don't think the language server is running at all, I get no suggestions e.g. for {{ partial:..., and attempting to run any of the plugin commands, e.g. Reload Statamic Project Details gives:
Impacted Products Which Antlers Toolbox products does this bug apply to?
- [x] Antlers Toolbox for VS Code
- [ ] Formatter CLI
- [ ] Antlers Prettier Plugin
- [ ] Antlers Syntax Highlighting (external systems - not VS Code)
Versions and Other Plugins/Extensions
- Visual Studio Code - Insiders: 1.100.0-insider
- Antlers Toolbox: 2.6.21
- Kubuntu: 24.10
I have disabled all other extensions and the problem remains.
To Reproduce Use the insiders build. The suggestions etc work fine on the non-insiders build.
Expected behavior Plugin to work.
Thanks for the report! Doing a quick dive, seems related to some imports on the Insiders 🤔
Yeah, sorry it's not a very detailed report! I don't usually use VS Code so don't know what I should be providing (e.g. logs), but your plugin is by far the best experience when working with Antlers.
Let me know if you do need anything more from me though.
No worries! I'll fiddle with it to see if I can figure what's going on with the Insiders build 🙂
FWIW, I decided to give VSCode a try (currently a PHPStorm user, but wanted to see what the Antlers Toolbox can do) and receive the same error, but on the standard download from the public Microsoft site.
Version: 1.100.2 (Universal) Commit: 848b80aeb52026648a8ff9f7c45a9b0a80641e2e Date: 2025-05-14T21:47:40.416Z Electron: 34.5.1 ElectronBuildId: 11369351 Chromium: 132.0.6834.210 Node.js: 20.19.0 V8: 13.2.152.41-electron.0 OS: Darwin arm64 24.5.0
Antlers Toolbox: 2.6.21 macOS Sequoia 15.5
Thanks for the extra info!
@martyf Just published v2.6.22 that should address that error message (as well as a few minor issues with auto-complete). I'll leave this open in the meantime 👍
Resolved for me, and working as expected, thanks John. Hopefully addresses @hailwood's issue too.