deno VS nvim-lspconfig

JSX can become valid, standardized ECMAScript syntax.

But first we need a valid syntactic sugar transformation, which I propose here.

Then we need to implement it in things like babel[0] bun[1] and deno[2].

Then, frameworks would adopt it as an optional alternative implementation.

Eventually, it could gain widespread support and become standardized.

[0] https://github.com/sdegutis/vanillajsx.com/blob/main/site/un...

[1] https://github.com/oven-sh/bun/issues/13630

[2] https://github.com/denoland/deno/issues/25312

Ha, in what I believe Ryan's first talk about Deno, he mentioned something about avoiding cute features or so, then he said Deno has URL-based imports "because they're cute". It didn't take long for someone to raise it up in 2018:

https://github.com/denoland/deno/issues/195

We've come full circle :)

So, does that work now? Can we simply npm run test? Really? Well, almost. Unfortunately, Node, in comparison to other runtimes like Bun or Deno still is JavaScript only, so we have to transpile from TypeScript it to JavaScript first.

Deno

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

QUIC is very exciting, after seeing what it can do for performance in Cloudflare network and Cloudflare workers, I can't wait to finally see it in Deno[0] 1.41.

[0] https://github.com/denoland/deno/pull/21942#issuecomment-192...

So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?

> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.

Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).

-- Learn about Neovim's lua api -- https://neovim.io/doc/user/lua-guide.html vim.opt.number = true vim.opt.tabstop = 2 vim.opt.shiftwidth = 2 vim.opt.smartcase = true vim.opt.ignorecase = true vim.opt.wrap = false vim.opt.hlsearch = false vim.opt.signcolumn = 'yes' -- Space as the leader key vim.g.mapleader = vim.keycode('') -- Basic clipboard interaction vim.keymap.set({'n', 'x', 'o'}, 'gy', '"+y', {desc = 'Copy to clipboard'}) vim.keymap.set({'n', 'x', 'o'}, 'gp', '"+p', {desc = 'Paste clipboard text'}) -- Command shortcuts vim.keymap.set('n', 'w', 'write', {desc = 'Save file'}) vim.keymap.set('n', 'q', 'quitall', {desc = 'Exit vim'}) vim.cmd.colorscheme('retrobox') require('mini.completion').setup({}) require('mini.files').setup({}) vim.keymap.set('n', 'e', 'lua MiniFiles.open()', {desc = 'File explorer'}) require('mini.pick').setup({}) vim.keymap.set('n', '', 'Pick buffers', {desc = 'Search open files'}) vim.keymap.set('n', 'ff', 'Pick files', {desc = 'Search all files'}) -- List of compatible language servers is here: -- https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md require('lspconfig').gopls.setup({}) require('lspconfig').rust_analyzer.setup({}) vim.api.nvim_create_autocmd('LspAttach', { desc = 'LSP actions', callback = function(event) local opts = {buffer = event.buf} -- Display documentation of the symbol under the cursor vim.keymap.set('n', 'K', 'lua vim.lsp.buf.hover()', opts) -- Jump to the definition vim.keymap.set('n', 'gd', 'lua vim.lsp.buf.definition()', opts) -- Jump to declaration vim.keymap.set('n', 'grd', 'lua vim.lsp.buf.declaration()', opts) -- Lists all the implementations for the symbol under the cursor vim.keymap.set('n', 'gri', 'lua vim.lsp.buf.implementation()', opts) -- Jumps to the definition of the type symbol vim.keymap.set('n', 'grt', 'lua vim.lsp.buf.type_definition()', opts) -- Lists all the references vim.keymap.set('n', 'grr', 'lua vim.lsp.buf.references()', opts) -- Renames all references to the symbol under the cursor vim.keymap.set('n', 'grn', 'lua vim.lsp.buf.rename()', opts) -- Selects a code action available at the current cursor position vim.keymap.set('n', 'gra', 'lua vim.lsp.buf.code_action()', opts) -- Displays a function's signature information vim.keymap.set('i', '', 'lua vim.lsp.buf.signature_help()', opts) -- Format current file vim.keymap.set({'n', 'x'}, 'gq', 'lua vim.lsp.buf.format({async = true})', opts) end, })

neovim/nvim-lspconfig: Quickstart configs for Nvim LSP

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

Adding language support it neovim isn't very difficult once you're setup. I use nvim-lspconfig[1] and just about any language you could need is documented[2]. But like others have mentioned there are batteries included distributions of neovim if that's your cup of tea.

[1]: https://github.com/neovim/nvim-lspconfig/

[2]: https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

If we can't find the basic usage in the documentation we can go to nvim-lspconfig's github repository. In there we look for a folder called server_configurations, this contains configuration files for a bunch of language servers.

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

This specific issue talks about fixing clangd for that error: https://github.com/neovim/nvim-lspconfig/issues/2184. The issue is ongoing for ccls AFAIK but for clangd, this has been discussed and fixed in the past already.

I am trying to set up the pbkit language server for protobuf files. Since it is not part of the nvim-lspconfig repo's server configurations, I have to figure the way out myself. It doesn't seem to be too difficult, as I can start from the bufls configuration there. The following is what I have at the moment:

I have configured neovim with lspconfig and mason. Added the suggested configuration of the lsp config(https://github.com/neovim/nvim-lspconfig) to ~/.config/nvim/after/plugin/lsp.lua Then I installed via mason the following language servers:

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.