ShellCheck VS shellharden

Unfortunately, this did mean that configuration began to sprawl. At this point, I had configurations not just for Vite (shared with Vitest) and tsc, but also for Prettier, ESLint and even ShellCheck. Many of these files had shared settings that needed to match each other. This was somewhat manageable, until Vite was also in the mix.

Shellcheck is another useful one (linter for shell scripts)

https://www.shellcheck.net/

There's now an issue for it https://github.com/koalaman/shellcheck/issues/3088

ShellCheck

It's been so long since I used it seriously I couldn't tell you.

There's over 1000 open issues on the GitHub repo, and over 100 contain "false positive". I recognize several of these at first glance.

https://github.com/koalaman/shellcheck/issues?q=is%3Aissue+i...

Reminder of the handy ShellCheck:

* https://www.shellcheck.net

Even if you don't follow or agree with its advice, it can be a handy and quick second opinion / sanity check.

If you're only occasionally writing shell scripts, Amber may not be a priority for you. In such cases, linting tools like ShellCheck could be more beneficial. However, if you find yourself frequently writing shell scripts, to the point where you're considering Python or Ruby for better re-usability, then Amber is definitely worth your attention.

As carlinigraphy points out, shellcheck [0] exists, and can easily be put into pre-commits, a CI pipeline, etc. This would have almost certainly flagged your problem immediately.

> I would be willing to learn a sane language, but bash isn't one.

It's a general language that has to be both an interactive interpreter and script executor, and it needs to support a huge variety of architectures and kernel versions, as well as historical decisions. It's going to have some cruft.

[0]: https://www.shellcheck.net/

These projects use Caddy as my local development server, Dart Sass for converting my Sass files to CSS, elm, elm-format, elm-optimize-level-2, elm-review, elm-test (only in Calculator), ShellCheck to find bugs in my shell scripts, and Terser to mangle and compress JavaScript code.

Complementary - https://github.com/anordal/shellharden/blob/master/how_to_do...

Everytime I see Shellcheck coming up, I have to mention shellharden[0] written by a colleague of mine. It is basically shellcheck but it applies the suggested changes automatically.

0: https://github.com/anordal/shellharden

Also worth mentioning shellharden

See also:

* https://www.shellcheck.net/ — linting tool to avoid common mistakes and improve your script

* Bash Practices: https://mywiki.wooledge.org/BashGuide/Practices

* Bash Pitfalls: https://mywiki.wooledge.org/BashPitfalls

* safe ways to do things in bash: https://github.com/anordal/shellharden/blob/master/how_to_do...

* better scripting: https://robertmuth.blogspot.in/2012/08/better-bash-scripting...

* robust scripting: https://www.davidpashley.com/articles/writing-robust-shell-s...

There is shellcheck, and shellharden which is a strict version of it. There are similar stuff here, some that also help with your editor. You can also use a docker version of shfmt. See here for a quick tutorial on shfmt.

Regarding linters, there are several of them in most languages.For bash, there is Shellcheck or a more strict (and sometimes confusing) Shellharden to do exactly what you want.

For example, shellharden looks awesome.