Swizec Teller - a geek with a hatswizec.com

    How JavaScript linters cause bugs

    I was doing code review for a coworker, and it soon became obvious that he used a linter and that the linter gave him a bright idea: use strict comparisons.

    Using strict comparisons is a great rule to follow. === instead of ==, !== instead of !=. Your life will be better.

    You're ensuring not only that your values are equal or unequal, you ensure their types match as well. Because JavaScript has funny types, strict comparison lets you avoid painful pain.

    Things like this:

    > "0" == 0
    true

    And like this:

    > true == 1
    true
    > false == 0
    true

    Even things as silly as this:

    > new Array() == 0
    true
    > [] == 0
    true

    Run a linter on those examples, and it will sagely say "Dude, use strict comparison. ALWAYS use strict comparison.”

    And your linter would be right. === fixes all of those examples.

    > "0" === 0
    false
    > true === 1
    false
    > false === 0
    false
    > new Array() === 0
    false
    > [] === 0
    false

    👌 Problem solved. 👌

    But here's one situation where it gets tricky. Checking undefinedness:

    > null == undefined
    true
    > null === undefined
    false

    Under loose comparison, null and undefined are equal. Under strict, they're not.

    Curated JavaScript Essays

    Get a series of curated essays on JavaScript. Lessons and insights from building software for production. No bullshit.

    Join 15,883+ engineers learning lessons from my "raw and honest from the heart" emails.

    ⭐️⭐️⭐️⭐️✨
    4.5 stars average rating

    This can cause all sorts of issues.

    Here are some examples I found in my coworker's PR. 👇

    const url = $(elem).data('url')
    if (url !== null) {
    // ...
    }

    But if your elem doesn't have a data-url="..." attribute, jQuery returns undefined, not null. Strict comparison fails.

    A better approach is to use if (url) because undefined is falsey and so is an empty string. That makes your code robust against data-url="" :)

    function scroll({ elem, offset, duration }) {
    duration = duration !== null ? duration : 2000;
    }

    But if you call scroll() without duration, it's undefined, and your code breaks. No default duration for you. A better approach is to use destructuring defaults, like this: function scroll({ elem, offset, duration = 2000 }).

    function get_id(widget) {
    let id = widget.id;
    if (id !== null) {
    // ...
    }
    }

    But reading an inexistent object property returns undefined, not null, and this code breaks. Once more, you're better of relying on inherent falsiness 👉 if (id).

    function createWidget(defaultText, onClick, markBusy) {
    new Widget({
    text: defaultText,
    onClick: onClick,
    markBusy: markBusy !== null && markBusy
    })
    }

    This one is tricky. It's trying to pass markBusy into the Widget constructor, but only if it's defined. You can't use default param values because there's no destructuring so hmm… 🤔

    Then again, the whole exercise is futile. You can achieve the same effect if you rely on inherent falseyness: markBusy: !!markBusy.

    I guess my point is that you have to be careful. Don't blindly trust your linter when it says change this code to that code.

    Happy hacking 🤓

    Did you enjoy this article?

    Published on September 14th, 2017 in Front End, Technical, JavaScript,

    Want to become a JavaScript expert?

    Learning from tutorials is great! You follow some steps, learn a smol lesson, and feel like you got this. Then you go into an interview, get a question from the boss, or encounter a new situation and o-oh.

    Shit, how does this work again? 😅

    That's the problem with tutorials. They're not how the world works. Real software is a mess. A best-effort pile of duct tape and chewing gum. You need deep understanding, not recipes.

    Leave your email and get the JavaScript Essays series - a series of curated essays and experiments on modern JavaScript. Lessons learned from practice building production software.

    Curated JavaScript Essays

    Get a series of curated essays on JavaScript. Lessons and insights from building software for production. No bullshit.

    Join 15,883+ engineers learning lessons from my "raw and honest from the heart" emails.

    ⭐️⭐️⭐️⭐️✨
    4.5 stars average rating

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Want to brush up on modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️