Preloading occurs when the visited route includes a lazy-loaded bundles, this feature was added in 19.1.0.

In this case, since there's a timer involved, we probably shouldn’t trigger preloading but the bundler lacks the contextual awareness. One possible solution is to enhance the Angular compiler to insert specific instructions into import statements: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import/with](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import/with

Ultimately, this would require compiler-level changes to annotate certain import calls with alternative behavior. Alternatively, we could simply avoid adding preloads for modules that aren't explicitly defined in the router configuration. However, this approach would prevent all deferred blocks from being preloaded, which may not be desirable.

As per the current documentation of the defer blocks, especially about prefetch, the alternative approach makes more sense to not preload deferred blocks until prefetch is specified. I can see how it can make it really confusing for developers to understand what @defer really does. I.e. does it download the javascript bundle on the on and when triggers? Or only render the component/load in the component tree when the triggers happen?

I think not preloading the deferred blocks makes much more sense. If someone wants to preload, they can use the prefetch keyword with their deferred blocks.

The documentation also doesn't mention that the default behavior is prefetch on idle.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}