-
Notifications
You must be signed in to change notification settings - Fork 12k
inline.js gets cached by the browser, which then caused issues in loading the right chunks #3082
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
Comments
I believe that is what #2899 fixed. Will be in next release. |
Good news. Any idea when the next release is due? Thank you so much. On Wed, Nov 9, 2016 at 3:51 PM, Kristofer Karlsson <notifications@github.com
|
New beta releases seems to be released every 1-2 weeks. The current release was released on October 28th. But that's no guarantee there'll be another released any day now. |
Fixed by #2899. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
The log given by the failure.
Mention any other details that might be useful.
In our Angular CLI app, src="inline.js" got cached by the browser, which then created issues in loading the right chunks.
The text was updated successfully, but these errors were encountered: