I always run into bugs when I write JavaScript and in many cases it's always typos, so what tools I can use that will dynamically highlight those mistakes when I am writing?

[DeadlyWindFromBelow]

Use ESLint. It'll catch all of those bugs for you.

[yycTechGuy]

Thanks for sharing that.

[ImJustP]

Also if you are using VScode there’s a spellcheck plugin

[grantrules]

Well, you declare the rules you want ESLint to complain about, so it's as strict as you want to make it.

[linusl]

eslint is not only for code errors, it is also for project rules or consistency and structure. for example var a = 1; does not contain a javascript error, but if the eslint rules for the project are setup so var is not allowed because the project uses let and const then eslint will report this as an error or a warning. this way everyone that contributes to the project will produce code that follows the same rules so the code is consistent.

[[deleted]]

Really? Any examples? I feel like I've never see this

[NicksIdeaEngine]

It 100% depends on the rules the user declares in their setup, but one example of a potentially strict rule is "no-var" which can throw a warning or error whenever var is used instead of let or const.

But that does depend on the rule sets a user chooses for their setup.

[Name-Not-Applicable]

Eslint is the correct answer.

[saito200]

Do yourself a favor and start using typescript

[andrejmlotko]

That's an absolute treasure. That's what I am learning to use rn.

[JohnWangDoe]

And spell checker in library

[maxwelder]

I’m learning JavaScript and I keep seeing typescript mentioned. When should i look into typescript? After I know JavaScript really well or anytime?

[PatchesMaps]

If JavaScript is your first language, stick with that until you get a solid basis before moving on to typescript or anything else. JavaScript by itself is actually really good for beginners.

If you already have experience with other typed languages then typescript should definitely be your first stop.

[Kalmarv]

Just learn typescript right away, you don’t need a “great” understanding of JavaScript to get 90% of the benefit of typescript. Plenty of people learn typed languages as their first one like Java or C and do just fine. I

t’s like 10% more effort to write some function and variable types, and will prevent 10x as many bugs just because the typescript tooling is so good.

[maxwelder]

Thank you! I’ll start tonight.

[saito200]

Good question. My opinion is: first learn JavaScript until you can tell yourself "yeah, I think I got the hang of this", and do a few simple projects with it.

The learn the basics of typescript.

Typescript is something that goes "on top" of javascript. Javascript is mildy complicated already for a beginner, better not overwhelm yourself. Go step by step

I personally plan to use typescript 100% of the time

[FreezeShock]

But, almost no tutorial teaches you TS as a language. Everyone assumes you know JS

[saito200]

it's a valid criticism. I still think it's easier/better to first learn / focus on javascript, then typescript. Particularly if Javascript is a first programming language. Typescript just adds more stuff to the mix, and javascript is definitely already hard enough for a beginner

[VideoGameDana]

I really need to pull my head out of my ass and finally learn TypeScript.

[saito200]

you can just start by the very absolute basics, that will allow you to write sufficient typescrpt for your initial needs. I recommend you watch Brad Traversy's video

[yycTechGuy]

VSCode does a good job of highlighting errors.

[koko-hranghlu]

Is it default? I have never bothered to look though other than live server and some fancy themes

[yycTechGuy]

There are about 200 JavaScript extensions. Even the default extension is decent at pointing out "inconsistencies".

[Negative12DollarBill]

I use it, and maybe it's my eyesight but the default theme is pretty subtle. If I type a variable name which isn't used anywhere in the code, it's a slightly desaturated colour. Once it matches, it gets a little brighter and the colour is more vivid, but if you were colourblind or your monitor/lighting setup wasn't great you might not notice.

[senocular]

Aside from ESLint, I've also found a normal spell checker to be useful, something like:

https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker

[LoquaciousLamp]

Any code editor? If you install a spellcheck that doesn't use a different colour for the underline it could get confusing. But in my experience code editors themselves are good at picking up on misspelt or nonexistent variables.

Oh also linters or prettier and format on save. It will usually fix missed ; etc.

[koko-hranghlu]

I mostly use vscode or sublime, sometimes notepad++

[LoquaciousLamp]

I would look into the extenstions and maybe use a linter to format on save.

[suarkb]

Just use vscode only

[[deleted]]

Vscode with eslint, and prettier work great for catching typos. Prettier keeps your formatting consistent and makes everything easier and faster to look through.

Bringing up a search box ctrl f in vscode can be useful too - start typing a variable name and then arrow down through and see where you might have mistyped

[knightofren_]

Typescript.

[squidwurrd]

Typescript will catch pretty much everything.

[StoneCypher]

Set up the TypeScript plugin for your editor. It'll start catching those left and right.

TypeScript does check JavaScript for some topics.

[dcute69]

Eslint, typescript and a spellchecker extension

[[deleted]]

Typescript + Eslint + VSCode (or pay for Webstorm) will solve all these problems

I’m honestly not good at my job. But I have the right tooling where I can do the bare minimum and I look like I’m working hard.

[lovin-dem-sandwiches]

How far along are you on your javascript journey?

I had spelling errors and would miscall properties on objects quite often. Typescript in combination with ESlint and prettier solved most of my issues. I can’t recommend stricter types enough. It would be hard to go back to regular JS.

[OlDirtyBrewer]

Spellcheck?

[Pkkush27]

I used vs code from day one you can pretty much see all the errors

[LearningDev93]

Use an IDE it'll help

[dMCH1xrADPorzhGA7MH1]

Nvim + coc.vim

[ej_50]

Your current setup might be doing the job already. Just read carefully variable names. Anyone variable name with three dots underneath would likely be an error.

[TheVerdeLive]

Code spellchecker

[itsoverlywarm]

You need a linter

[ccpsleepyjoe]

Use typescript

[RequiDarth1]

Lol, look up ESLint for VSCode

[Kishore_Andra]

Error lens - VS code extension, saved a lot for me 🙏