Open akoidan opened 5 years ago
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 experimentalDecorators generated InputEvent to the resulting js file
because an empty Vue + TypeScript project compiled and bundled (with instapack) has no InputEvent
keyword in the resulting JS:
@ryanelian , could you please check vue-webpack-typescript repo. Please do the following
git clone https://github.com/akoidan/vue-webpack-typescript a; cd a
git checkout tspoly
yarn install
yarn run build
cat dist/main.js |grep InputEvent
p.s. It's so weird to see white scheme in VsCode :+1:
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: