Spell-checking isn't just for documentation.
We move fast as developers. It's one thing to make a spelling mistake in documentation. Spelling mistakes in your code can lead to bugs. Bugs that could have been easily avoided with the help of a code spell checker.
One of my favorite VS Code plugins is Code Spell Checker. It's been a total game-changer for me. It catches spelling mistakes by putting that blue little squiggly line underneath misspelled words.
It's even smart enough that it uses casing to determine where word breaks should be. (Look at the example above and notice that only the misspelled
Compnoent is underlined, while
My is left alone.)
And there's also user and workspace dictionaries to capture those weird words that should be treated as actual words, like Eleventy.
Even if you don't use VS Code, there's likely a plugin to help you with code spell-checking in your editor of choice.
If you’re constantly copying and pasting and losing what is on your clipboard, here’s the perfect solution!
Sharing GitHub commit hashes directly works for ephemeral uses, but there is a safer way for links that need to last.
Learn how to run a single test within a file, how to target a series of tests within a file, or how to only target a single file when using Jest.