github.com/eslint/eslin...

It is *wild* how simple that change is for that kind of startup perf boost 😍

Main reason why I wrote this is because I've tried this API for a work-related task before, but it didn't work out at all.

Reasons explained in `Is It a Navigation?` section

Is this documented somewhere?

And now, we can format without having to focus too much on the tools that we use.

I hate when people starts to `pls migrate to Y, X sucks now!` every time these kind of tools comes out.

They're forgetting the main purpose of these tools: make your code great

Lately, we also have eslint-react (www.npmjs.com/package/@esl...), which applies ESLint rules for your React-based projects without being too binded to `react-dom`

First, we have Anthony Fu's ni (github.com/antfu-collec...), which makes you ignore package manager wars.

You can use ranges too! VitePress has integrated a lot of Shiki transformers internally.

vitepress.dev/guide/markdo...

Day 21. We can (again) extend the previous day functionality.

We can check if an element exist in an array using `extends`

Day 20. We can re-use the parser code from the previous day. But we do need to implement the result object logic.

Day 19. The trick here is to parse the line one-by-one and trimming them.

Day 18. We are dealing with unprovided generics.

The trick is to assert whether the generic is provided or not. If it's not provided, access the array element. Otherwise, return the generic as-is.

Day 17. We can strongly-type the composition and utilities using generics.

To avoid type narrowing for string utilities, we can recast it using string utility types.

Day 16. We can deal with recursion with the help of `ReturnType`