-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Time to drop legacy support for IE? #413
Comments
So is this project ... it's maintenance mode and I don't have capacity these days to remove stuff that's not breaking anyway. If you find the time to file a PR I'd be happy to publish a major 👋 |
so is the recommendation to switch to something like uhtml instead? |
I don't know ... even uhtml is pretty much done, but surely the only library I currently care about of that kind (template literal based one) ... this one has great stability which is why I don't care much touching code that won't ever bother anyone but those looking for modern alternatives maybe should migrate as this was my first attempt at template literals DOM manipulation, all libraries used in here have been substituted here and there and this is maintenance mode for projects that just work and never had bugs with it but, if they do, I am here to help (most notably folks using it to fuel Ad Blockers and hundred million users to date). |
While looking at the dependencies of hyperhtml i found things such as:
weakmap, customEvents, trim, Map, WeakSet, isArray polyfills for really old browsers.
i think this should be optional for developers to opt in to.
IE is pretty much dead now already.
The text was updated successfully, but these errors were encountered: