Modernizr

[jt3k]

Please explain how you replace the Modernizr with @babel/preset-env

Do the creators of Modernizr know that they are not recommended? =)

[slikts]

The preferred alternative to feature detection is polyfilling, and @babel/preset-env is the simplest way to polyfill. Modernizr hasn't been relevant for a long time.

[jt3k]

are you really sure that @babel/preset-env can detect mix-blend-mode or cssgrid support and provide this information inside my css file?

[rejas]

I agree with @jt3k Modernizr still has some features that cant just be transpiled or polyfilled.

[slikts]

The legacy browser market share keeps shrinking, so the complexity of having branching logic based on feature detection for legacy browsers is increasingly not justified. The idea is to have recommendations for general use cases, and in general polyfilling should be preferred, even though it doesn't replace feature detection for every use case.

Here's a graph that tells the same story; specifically, that Modernizr hit its peak when the legacy browser presence was much more significant.

[jt3k]

I see that both searches are popular in my country(Russia). But in the end, it's up to you.
Let’s at least add under the paragraph with modernizr why it is not recommended, and make a link to this issue

[slikts]

The trend looks about the same in Russia. I've added a link to this discussion.