Being a bash developer in the 21st century

• null-ls.nvim

  164 3,554 0.0 Lua

  Discontinued Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.

you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)

here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...

• bash-language-server

  23 1,937 9.4 TypeScript

  A language server for Bash

  

In neovim I would recommend setting shellcheck with null.ls or using the bash language server: https://github.com/bash-lsp/bash-language-server

both work really well

• WorkOS

  workos.com sponsored

  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.

  

• asdf

  340 20,448 7.9 Shell

  Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more

  

• bash3boilerplate

  4 2,071 7.1 Shell

  Templates to write better Bash scripts

I'm a fan of Bash3 Boilerplate (https://github.com/kvz/bash3boilerplate) and use a modified version of it for my shell scripts now. I like the code style and the logging, although I've amended the logging slightly to add a pipe input for long running processes that you want to see the output from before it finishes.

I prefer having a stop-on-unexpected script as it makes errors far more explicit and it's not too onerous to work round the peculiarities of return codes.

Greg's wiki (https://mywiki.wooledge.org/) is my go to resource for looking up snippets and learning to avoid the footguns - that and shellcheck are the key to "robust" bash scripts.

Suggest a related project