In the case of code-splitting, it sometimes doesn't make RPC calls when the user navigates around. Rather, it tries to load the .cache.js files required for the "page" the user is navigating to. In the case where a new version is deployed and the user hasn't refreshed, these files of course won't exist. How do you handle this gracefully?
We're using AppEngine so new versions don't have the old .cache.js files by default.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/tKa_PyIVuFUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment