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

For those who are not comfortable with the current documentation, we are working on a second version with a better structuration and simpler/clearer code+examples.

Roadmap:

• new navigation tree
• write / review getstarted section
• write / review advanced section
• write / review plugins section
• fix css stuff (header clickable zone, links highlight, nav, ..

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-

This check https://github.com/GoogleChromeLabs/preload-webpack-plugin/blob/master/src/index.js#L118 breaks when the plugin is used with Expo that extends HtmlWebpackPlugin class into ExpoHtmlWebpackPlugin.

Is there a better way to find the plugin instance?

Is the timeout option per route? I tried it with a 10 second timeout (10000ms) and it didn't seem to delay the loading of the route at all. I'd love to see a working example in the repo.

React supports rendering of iterables and collections as childrens. react-tree-walker does not support this at this moment leading to unexpected results when using Iterables (e.g. List from immutable-js) as children. Subtrees that are rendered in react are might be skipped by the visitor.

I created a minimal example that shows the issue: https://codesandbox.io/s/o9kzlrql86

Here are som