-
Notifications
You must be signed in to change notification settings - Fork 7
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
Input event #6
Comments
Hi, thanks for reporting an issue. Is this something about the DOM library? Unfortunately, my TypeScript lib polyfills do not cover DOM libraries (https://github.com/ryanelian/ts-polyfill/tree/master/src) (for obvious reason: because core-js itself does not ship with DOM polyfills...), which means this issue falls outside the scope of this project. That said, I'm willing to help you out with this issue. I'm trying to understand what you meant by |
@ryanelian , could you please check vue-webpack-typescript repo. Please do the following
p.s. It's so weird to see white scheme in VsCode 👍 |
Prelude:
I (and many other developers) rely on this package + target es5 in tsconfig.json that everything would work on ie11, edge 15 and etc, while recklessly developing in Chrome.
The thing that I found out,
experimentalDecorators
generatedInputEvent
to the resulting js file. And it just crashed on production in Edge 15, despite I didn't even use the ReflectMetadata package. I blindly did what guide in other libs tell, enabling magic property in tsconfig (experimentalDecorators
). I'm telling all of these because that what other devs might face.Yeah, of course, that happened by my fault because I wrote code, not even expecting that typing could break anything:
What I propose is to have something like these, to reduce those kinds of risk:
The text was updated successfully, but these errors were encountered: