Is the any #eslint/#typescript plug-in to enable a rule so that anonymous objects are forbidden? I’d like to make sure that all objects are backed by a type. So, disallow something like const foo = { a: 5 }. Is it possible?

To make #TypeScript ensure you're writing safe code, you need to properly configure it, but proper configuration is really messy, and tools like #ESLint don't even support it. So you are left with the single TSConfig that makes TypeScript lie and deceive you.

This is the state of modern #JavaScript development experience.

I've got such a weird problem; it looks like #eslint is running in it's own thread. So when running `yarn lint` it finishes, then 5 seconds later it takes over the console again with the actual output. This is causing havoc!
Any ideas? #JavaScript #JS #Code

https://blog.bitsrc.io/why-is-my-jest-suite-so-slow-2a4859bb9ac0

I learned:

* to link the Chrome profile with Node scripts to profile performance
* using an eslint rule to NOT import from index files in tests
* that setupTests.ts runs NOT once ,on the startup of all tests
* to deactivate type checking for the tests

#es6 #js #javascript #ts #typescript #react #jest #babel #webpack #performance #test #unittest #profiling #eslint

Them: "we can't start to #eslint the #TestAutomation code now, the tests are all flakey or unstable"

Me: "perfect, if the tests are already broken we don't need to worry about breaking them even more"

> Why is #Rust now being used to replace parts of the JavaScript web ecosystem like minification #Terser, transpilation #Babel, formatting #Prettier, bundling #webpack, linting #ESLint, and more?

https://leerob.io/blog/rust

#es6 #js #javascript #webdevelopment #frontend #webdev