Neither do I but it's what drives the syntax support in Visual Studio Code :)
So, even when just working with JavaScript, you may still get errors in VSC - even though it will run absolutely fine. It can throw some red herrings for devs who aren't aware why, so just thought I'd mention it.
Not for what I'm talking about, no. Whether TS and Babel can work, when writing TS, is a question for someone that uses TS :)
I'm referring to the VSC built-in JS/TS validator. It can be disabled by updating the settings.json file to include "javascript.validate.enable": false and/or "typescript.validate.enable": false. If they are disabled ESLint can take over and show the appropriate errors.
Neither do I but it's what drives the syntax support in Visual Studio Code :)
So, even when just working with JavaScript, you may still get errors in VSC - even though it will run absolutely fine. It can throw some red herrings for devs who aren't aware why, so just thought I'd mention it.
Not for what I'm talking about, no. Whether TS and Babel can work, when writing TS, is a question for someone that uses TS :)
I'm referring to the VSC built-in JS/TS validator. It can be disabled by updating the
settings.jsonfile to include"javascript.validate.enable": falseand/or"typescript.validate.enable": false. If they are disabled ESLint can take over and show the appropriate errors.Ahh okay yeah, that's true!
VSC will show an error if you don't configure it!
I just got used to seeing the error 🤣