-
Notifications
You must be signed in to change notification settings - Fork 339
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
Consider dropping Universal Module Definition (UMD) bundle #180
Comments
@frederikprijck to get back to your earlier comment #174 (comment):
My main issue is long term maintenance, this code will be around for the entire 4.0 lifecycle, and it's an afterthought for most if not all tooling these days. Realistically those that are still using UMD are very unlikely to be actively maintaining projects, let alone upgrade and perform migrations (such as #175).
The thing is, if we are deciding to make these users perform the aforementioned migration steps, we might as well take the extra step and pull it entirely. Especially since this will only be used in legacy applications. |
Update, we're looking to perhaps keep the UMD bundle backwards compatible (#181), so this might soon not be relevant anymore. |
Thanks for moving this into an issue.
We do support UMD in pretty much all of our JavaScript SDKs, and want to keep that if it doesn't cause any current issues.
Legacy applications shouldn't mean they are unable to use our SDK. |
Closing this for #181 |
Checklist
Describe the problem you'd like to have solved
Since version 4 of this library is going to contain breaking changes (#175) to the Universal Module Definition (UMD) bundle, we might want to consider dropping it entirely. UMD was imagined when there were no module loaders on the web, which is no longer true now that we have JavaScript modules.
Describe the ideal solution
Remove the UMD bundle and recommend users to use the official module system that JavaScript provides.
Alternatives and current workarounds
Keep distributing the bundle, which likely nobody will use as it would require an explicit upgrade and migration steps.
Additional context
See discussion under #174
The text was updated successfully, but these errors were encountered: