rustup.rs VS cspell

Much of the time that people are writing shell scripts, they're writing them not because they prefer shell syntax to that of some other language, but rather because they're creating a script that needs to be widely disseminated/deployed to all sorts of machines with unpredictable install bases.

This is why a large fraction of the shell scripts that exist in the world still hold to Bourne shell syntax, rather than using any of the syntax extensions from its descendant shells — Bourne shell (or at least, something at /bin/sh that interprets Bourne-shell syntax) is part of the POSIX standard. So you can expect any POSIX system — no matter how weird — to be able to run (Bourne) shell scripts. You can run them on Alpine. You can run them on Busybox. You can run them on your NAS. You can run them on your router. You can run them in your initramfs, on your Kubernetes nodes, on your Mosix nodes, whatever.

For an example of the type of script I'm talking about — see e.g. the script you download+run when you run the command-line on https://rustup.rs: https://github.com/hsivonen/rustup.rs/blob/master/rustup-ini...

There's absolutely no benefit that this script gets from being written directly in POSIX-compiliant Bourne shell syntax, rather than being written in something that compiles to it; any more than programs for your PC would benefit from being written directly in ASM rather than in something that compiles to it.

CSpell is a great spell checker for code. It can be added as a source to null-ls. However, a lot of features are missing when it's used from null-ls, for instance the ability to ignore certain paths. According to this comment in a null-ls thread cspell would need its own companion plugin.

I use cspell CLI to test for spelling errors at build time so that spelling errors cannot get committed. It's very easy to automate to avoid introducing errors. I don't know of an offline library to check for grammar though.

Spell check

Are this.state.representative and this.respresentative supposed to be the same thing? First off, they are misspelled, second, not the same property. Highly recommend at least using a code spell checker cspell and VS Code - Code Spell Checker if you aren't going to use TypeScript or ESLint.

You could definitely use a spellchecker. cspell is a great programatic spellchecker that you can add to your commit or build validations to enforce that things are spelled correctly.

- cspell: https://github.com/streetsidesoftware/cspell/tree/main/packages/cspell

Also, it's response not responce. Highly recommend using the Code Spellchecker plugin for VS Code and/or the cspell cli for spellchecking.