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
Loading the polyfill on Chrome 67 will raise a warning #18
Comments
I'm not sure how that's possible; the shim isn't using appcache in any way. However, that warning only pops up on HTTP pages - your project (every project) should be on HTTPS regardless. What's on line 51 of index.js? |
I am using https://github.com/facebook/create-react-app which uses Webpack under the hood.
I confirm that the line |
How can you confirm that? The error is on line 51; you’re doing an import of it on line 51? |
Ohhhh i think i see the issue, it’s inside object-keys. If you import object-keys instead of this package, do you get the same warning? If so, please file an issue on https://github.com/ljharb/object-keys and i can address it there. |
I am using JS modules, the line 51 mentioned in the warning is from the bundle generated by Webpack.
You will see the warning in the console. |
@ljharb you are right! |
I am closing this issue an opening a new one: ljharb/object-keys#46 |
When using this code in my project:
I will see this warning in Chrome 67.0.3396.87 console:
index.js:51 [Deprecation] Application Cache is deprecated in non-secure contexts, and will be restricted to secure contexts in M69, around September 2018. Please consider migrating your application to HTTPS, and eventually shifting over to Service Workers. See https://goo.gl/rStTGz for more details.
The text was updated successfully, but these errors were encountered: