Cors fix #51
Merged
Cors fix #51
Conversation
This file contains 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
yochannah
approved these changes
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR authors: @LakshSingla
Please describe your PR:
This PR aims to fix the CORS issue, which persists when
imjsis included in a bundle. The branch is also published as an NPM package, via my account, to ensure if it works, when pushed to NPMTo install that package, run
npm i -save @lakshsingla/imjs-corsand userequire '@lakshsingla/imjs-cors'wherever you will userequire 'imjs'Reviewers: @amand1996 @yochannah
Review checklist: