developer.chrome.com VS typescript-eslint

Keep up with all the latest landings in CSS and HTML right here on developer.chrome.com and check out the I/O videos for more web landings.

Hola developers and learners 👋👋!! We are going to start a new blog series on Chrome Developer Tools. As a web developer, you know that having the right tools can make all the difference when it comes to building high-quality, efficient websites. But fear not! Chrome DevTools Elements section is here to save the day, like a superhero swooping in to solve all your web development woes 🦹.

developer.chrome.com https://developer.chrome.com › docs Lighthouse overview - Chrome Developers

Read the documentation https://developer.chrome.com/docs/extensions/. Build an MV3 for each API. File issues https://github.com/GoogleChrome/developer.chrome.com when you find inaccurate content.

where that is not what is really going on, because Chrome and Chromium browsers do not support capturing system audio. At best the audio captured is the tab audio. Try to capture the system audio produced by window.speechSynthesis.speak() and see what happens, see https://github.com/GoogleChrome/developer.chrome.com/issues/3957 https://github.com/GoogleChrome/developer.chrome.com/pull/3947#issuecomment-1274250421

developer.chrome.com

Keep in mind that getDisplayMedia() does not capture all audio output to speaker or headphones, e.g., does not capture window.speechSynthesis.speak() output, which is not output via the Tab audio, see https://github.com/GoogleChrome/developer.chrome.com/issues/3957.

Yep, they just updated when CWS stops accepting MV2 updates to January 2024: https://github.com/GoogleChrome/developer.chrome.com/pull/38...

Visit any website on https://developer.chrome.com or https://docs.microsoft.com

Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".

> Only lint files that have changed? How hard that is?

Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.

The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.

[0] https://github.com/typescript-eslint/typescript-eslint

By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):