Semicolons and using 'standard' with React/client-side Javascript

[karloespiritu]

I'm using standard for all of my new Node.js projects, and it works great so far. I'm wondering if standard would also be ideal for React projects. I really like using standard as my linter because I prefer my JS code without the semicolons.

Based on the standardjs docs, the only gotcha with omitting semicolons is when starting a line with (, [, or `. And then, I came across this discussion - https://forum.shakacode.com/t/es6-airbnb-style-guidelines-and-semicolons/235

It was mentioned by someone from AirBnb that these three characters are NOT the only gotchas, but also -- arithmetic operators and template literals.

I also noticed that most React-based projects, including Facebook's create-react-app project still use semicolons. Most of the boilerplate projects for React use Airbnb's JS style guide, which requires using semicolons and dangling commas.

My question is -- Will there be any issues if I use standard as a style guide for React or any client-side Javascript code that is transpiled to ES5?

It would be really nice to use standard for React/client-side javascript projects so I can unify my JS code style guide for both Node.js and React. Thanks.

[dcousens]

Will there be any issues if I use standard as a style guide for React or any client-side Javascript code that is transpiled to ES5?

Nope 👍

standard will warn you about any of the crazy gotchas thanks to eslint.

[Guria]

@karloespiritu just try this on cases on demo. Both arithmetic operators and template literals emit warnings.

[karloespiritu]

Awesome thank you very much @dcousens @Guria for the confirmation. 👍 I'll proceed with my plans to use also standard for my React projects. I will finally have a unified code style guide for Node.js and React. 🍻

[LinusU]

Glad to hear it 🙌