🚀 Feature Proposal

Move this check https://github.com/fastify/fastify-plugin/blob/78539fe08010a039f1d16e34f42807b51e240242/plugin.js#L109-L111 from fastify-plugin to fastify itself.
This would have the consequence of adding semver as a dep, but I think it does not matter much (fastify-plugin is ubiquitous anyway).

The check must happen at the beginning of https://github.com/fastify

DNS preanalyze is a way to reduce DNS analyze time:

<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />

Feedback from @surma:

I feel like by default you should add a rootMargin to the IO to trigger the load before something comes into the viewport.

So, rootMargin defaults to "0px 0px 0px 0px", meaning the intersection will be computed between the root element's unmodified bounds rectangle and the target's bounds. This change would be made to https://github.com/GoogleChromeLabs/quicklink/b

Current gjson version is 1.1.3 which is from late 2018 and lacks several features such as:

• Modifier @flatten to transform a json [1, [2, 3]] to [1, 2, 3] https://github.com/tidwall/gjson/blob/master/SYNTAX.md#modifiers
• Join multipaths https://github.com/tidwall/gjson/blob/master/SYNTAX.md#multipaths

There's a lot of place for improvement of the documentation.

• Update the Angular guide to use ngx-build-plus
• Improve the API documentation explaining the configuration properties
• Include a guide showing how to use Guess.js with JWT instead of OAuth
• Include Gatsby guide

The content of the documentation is in the GitHub page [repo](https://github.com/guess-js/guess-

For each Job, it adds plots about density, cumulative mean, and so on. But two files are named BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--density.png and BenchmarkDotNet.Artifacts/results/MyBench.Sleeps-Time50--facetDensity.png, with the -- instead of single. Like some iteration variable is empty (since later there are names with -Default-
![image](https://user-images.github

Something that could help the documentation would be a glossary that certain terms could link to. A pointer would be a good candidate, or C data structures (struct/union) in general. Also extension type, terms like extern or inline, etc. It wouldn't have to replicate a complete specification o