-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add ES5 syntax check for UMD builds #5301
Add ES5 syntax check for UMD builds #5301
Conversation
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.
Thanks! I think it would be good to get es-check
as an actual dependency though so that it's using a specific version, and then it could also be called in existing package.json scripts
8c92760
to
7ba1395
Compare
Thanks for the review @tjenkinson. I've made the requested changes. I'm not entirely sure why there are so many changes to the package-lock file... it seems most are related to the |
because renovate will keep it updated
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.
LGTM! although we can't merge it yet given that the new check correctly fails atm
refs #5299
We could wait for #5299 or merge it into there/temp branch for me to rebase that PR. |
Merged into working branch. Adding to #5299. |
* task/es5-check: Add ES5 syntax check for UMD builds (#5301)
) * Convert build packager to rollup * Add an es module target (#2910) * UMD build worker injection (#5107) * Add ES5 syntax check for UMD builds (#5301, #5288) * Add common rollup config * handle `self` not existing (happens in nodejs. The check that makes sure the dist file can be required in node and not throw was failing because of this.) * Disable coverage in CI * Add `config.workerPath` option and "hls.worker.js" build output (#5107) * Include transmuxer-interface id ("main" and "audio") in Web Worker setup and error logs Co-authored-by: Tom Jenkinson <tom@tjenkinson.me>
This PR will...
Add a build time check to verify UMD builds are valid ES5 syntax.
Why is this Pull Request needed?
A regression was unknowingly introduced in the v1.2.5 release that caused builds to no longer be compiled to ES5.
This type of check could have caught the issue.
Are there any points in the code the reviewer needs to double check?
This should fail until the build output is corrected.
Resolves issues:
Checklist