-
Notifications
You must be signed in to change notification settings - Fork 233
Create two different output js files on with vendor polyfills and one without #92
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
|
cc: @lahuey |
|
@muthurathinam Can you add package, which will get generated after this change, as a comment here? |
|
Output files:
|
MIchaelMainer
left a comment
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.
Please add information in the readme about the two output files.
… and one" This reverts commit d16fdfc.
without. 2.Update README.md file
… and one" This reverts commit 57ee9b6.
|
@MIchaelMainer I have updated the README.md file. |
darrelmiller
left a comment
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.
Looks good to me, although this is way out of realm of experience, so don't put too much weight in my opinion!
Two output js files are created
Polyfills for fetchapi and es6-promises are more common, so the host applications might already have the copies of these polyfills. Having ouput without polyfill will actually reduce the sdk file size which fastens the js loading.