-
Notifications
You must be signed in to change notification settings - Fork 543
chore(examples): use local polyfills when possible #6076
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
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 51cf925:
|
78aa494
to
bed9085
Compare
Redrafting the PR, since this morning even the pinned version of the polyfill.io URL fails. |
2567a45
to
51cf925
Compare
module.exports = { | ||
flavors: ['js', 'js-umd', 'react', 'vue'].filter( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's a small chance this is used in jsdoc type somewhere, do you mind checking? not sure if I changed it to string at a later point
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked at the current codebase and commits in the change history of this file, I could not find anything.
Summary
For our e2e tests we add polyfills in e-commerce examples, to include unsupported methods in IE11. This PR replaces remote polyfill links with local scripts.
Important
With this PR, IE11 testing is only performed on InstantSearch.js (
js
andjs-umd
). This change is temporary.→ Passing CI