Edge Browser Compatible #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not sure why this was breaking compatibility with Edge, spread syntax is supposed to be supported by Edge.
I believe the issue is crypto is a member of Window, so it is not accessible in a worker.
Polyfill for Edge.
|
I thought I saw somewhere that Edge finally supports spread. If it still doesn't, then Microsoft reverted back to its old ways and is letting Edge rot. |
|
CanIuse.com says spread is supported by all Edge versions. So, I am not sure why it was causing problems, and at one point the error said imports.env is not an iterable. Not sure why the error was inconsistent either, but it mostly said expected a string or an identifier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few minor changes to make it compatible with Edge.