-
-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider putting back prefetch function. #196
Labels
Comments
Hello @AoDev, I understand your concern. I will consider adding it back, it is true that the use-case is not covered. |
👍 for this feature 👍 |
gregberge
added a commit
that referenced
this issue
Feb 5, 2019
gregberge
added a commit
that referenced
this issue
Feb 5, 2019
gregberge
added a commit
that referenced
this issue
Feb 5, 2019
fivethreeo
pushed a commit
to fivethreeo/loadable-components
that referenced
this issue
Nov 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🚀 Putting back prefetch functions.
Motivation
Before, I could control manually when to download a chunk / component.
This allowed me to have a fast app boot / login screen. Then I could tell manually to fetch the "Private" section. This would result in really smooth UX. Switching to Private section would be instant.
In the 5.x breaking change, we are told to use "Webpack magic comments." But Webpack does not allow to do the above. At least, I could not find it.
We can just set
/* webpackPrefetch: true */
. We are left with the "good will of the browser" and in my case it's just a step back as the switch to the Private section now is not downloaded by the browser in time and results in worst UX.Pitch
Unless there is an alternative that I don't know about, I'd like to see this feature back until Webpack is able to let us load manually a chunk / component, since it allows superior performance in some cases.
The text was updated successfully, but these errors were encountered: