why many examples of javascript still using 'var' instead of 'const' and 'let'?

user_14629776 0
Viewed 1509

Such as cubejs:

<script>
  var cubejsApi = cubejs(
    'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1NTIzOTk5MjcsImV4cCI6MTU1MjQ4NjMyN30.SOO-A6GfGH7ar3EoeBb0cjj10BVxO3ffjvmqQziXIZA',
    { apiUrl: 'http://localhost:3000/cubejs-api/v1' }
  );
 ...
</script>

Such as the example of vue or nodejs Should I use 'var' nowadays?

node.js var javascript
2 Answers

Still a year or two back, Babel was still transpiling let and const to var, albeit, if it find two variables or constant declared with let and const respectively across different blocks in the same function, it would be given different names, to avoid clashes.

The main reason for transpiling to var was, few browser weren't updated to support ES6 syntax. Currently, most of the browsers support ES6/ES7 codes without transpiling, Firefox even supports some of the 2021 feature. You can check the compatibility here.

The reason why there are many codes and examples still use var is because, not every dev has gone through their repos and updated the code.

So should you use var now?

No! Unless there's really, really, reeaaally a specific reason for you to use var, use let or const. Even if you find a reason to absolutely use var, perhaps blame your coding style and change.

user_93999780

const and let is better in the majority of cases, but there are still a few cases where var is more correct.

For you question directly, var is probably still used for legacy reasons. It is supported in all versions of JavaScript and it would be a bother to change every example on the internet.

The only real advantage to var is it's compatibility. If you are writing for old platforms like .HTA tools or you must support older platforms like old phones or simply old browsers, then var is your only real option.

user_52427390
Related