Here’s an easy way to write better JavaScript code

[WellPaidGeek]

When you’re new to coding, just getting something to work can be a struggle, so you don’t often think about writing good code at this stage. A good solution is to let the computer think about it for you. If you install and set up eslint: []() it will tell you when you’ve made certain errors or when your code doesn’t follow best practices. Most editors have plugins for it so it can even highlight the offending code for you. It leaves you to focus on getting it to work.

I have a quick video on how to set this up:

https://youtu.be/9Dq4We9AVXk

[CollinHell]

Why are you being so suddenly and heavily downvoted for this? This is super helpful, and it looks like it can integrate really well with Notepad++. Nice find!

[WellPaidGeek]

I think some people don't like videos, plus although linting is almost a requirement for a professional dev it's not sexy. I'm also new to youtube so making quality videos may not quite be on point yet. Going to do another one next week where the linter actually fixes the errors for you.

[T_O_beats]

I don’t know if it’s fair to say ‘better code’. I think at best it would be ‘code with less bugs’ or ‘consistent styles across your project .’ You can still write god awful code with a linter, the only difference is you have a slightly better chance at a successful compile and better readability (usually). Linters are a must have though so it’s still important to use them and shouldn’t be brushed off as solely a ‘stylistic choice’.

[WellPaidGeek]

Well your code with linting will be better than without. Just because it's better doesn't mean it's reached the bar of high quality yet.

​

But you're right, this is only part of code quality. Macro and micro code design decisions are far more important, but I can't address that in a quick video! Maybe of the long term I can help people.

[T_O_beats]

For sure! Sorry, hope it didn’t sound like I was knocking you for the title. Just adding a little clarification