Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
neodev.nvim
💻 Neovim setup for init.lua and plugin development with full signature help, docs and completion for the nvim lua API.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I have no affiliations, but I think teal would be a great such language. It feels very much like "what TS is to JS" in that it's syntax is (I believe) a superset of lua, and it is possible to require teal files in lua files by first requiring the teal compiler (a one line change). In fact, there's already a neovim plugin that I use everyday written in teal! Teal also has the concept of declaration files (like `.d.ts` in TS or `.pyi` in python), and it has [declaration files for neovim files](https://github.com/teal-language/teal-types/tree/master/types/neovim) already. However, its LSP is very, very young.
I have no affiliations, but I think teal would be a great such language. It feels very much like "what TS is to JS" in that it's syntax is (I believe) a superset of lua, and it is possible to require teal files in lua files by first requiring the teal compiler (a one line change). In fact, there's already a neovim plugin that I use everyday written in teal! Teal also has the concept of declaration files (like `.d.ts` in TS or `.pyi` in python), and it has [declaration files for neovim files](https://github.com/teal-language/teal-types/tree/master/types/neovim) already. However, its LSP is very, very young.
I have no affiliations, but I think teal would be a great such language. It feels very much like "what TS is to JS" in that it's syntax is (I believe) a superset of lua, and it is possible to require teal files in lua files by first requiring the teal compiler (a one line change). In fact, there's already a neovim plugin that I use everyday written in teal! Teal also has the concept of declaration files (like `.d.ts` in TS or `.pyi` in python), and it has [declaration files for neovim files](https://github.com/teal-language/teal-types/tree/master/types/neovim) already. However, its LSP is very, very young.
I have no affiliations, but I think teal would be a great such language. It feels very much like "what TS is to JS" in that it's syntax is (I believe) a superset of lua, and it is possible to require teal files in lua files by first requiring the teal compiler (a one line change). In fact, there's already a neovim plugin that I use everyday written in teal! Teal also has the concept of declaration files (like `.d.ts` in TS or `.pyi` in python), and it has [declaration files for neovim files](https://github.com/teal-language/teal-types/tree/master/types/neovim) already. However, its LSP is very, very young.
If you use the sumneko Lua language server, you can add doc-comments that tell the server what type everything is supposed to be. It will then give you diagnostics based on those assumptions.
This plugin from our savior folke might help. The sumneko LSP doesn't know all the annotations for the built-in vim-namespace, but this plugin provides them.