strict

[SimonLab]

http://eslint.org/docs/rules/strict

strict: 2

I'm not sure about this rule, I think it can add more checks and good practice by using it but we also have all the other eslint which let us know if something is wrong

[eliasmalik]

I think we should have strict mode, it does more than add checks, it turns mistakes that may fail silently into actual errors.

[nelsonic]

Many of the 'use strict'; checks are also performed by the linter...

See:

• https://www.nczonline.net/blog/2012/03/13/its-time-to-start-using-javascript-strict-mode/
• http://stackoverflow.com/questions/1335851/what-does-use-strict-do-in-javascript-and-what-is-the-reasoning-behind-it
• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode

What we need to know what additional benefit we get from including a 'use strict'; in our files...?

[eliasmalik]

@nelsonic from a quick scan of those articles,

• Prevents this coersion and accidentally calling constructors without new
• Throws when trying to assign immutable properties

I agree that most of the issues covered by strict mode are also covered by the linter. But having strict mode on as well provides a level of redundancy. We know that we may change some of the linter rules in the future. It's nice to have the freedom to be able to do that without worrying about that same change introducing a vector for weird run-time bugs.

I'm happy to be persuaded to turn this off, but at the moment I think it's a good thing to have.