Andreas
Andreas
and https://github.com/webpack/webpack/issues/7425
@aze3ma Did you have any chance to look into this?
@martinoss Unfortunately there is no plan/time to maintain `react-app-rewired`: https://github.com/timarney/react-app-rewired/issues/162#issuecomment-417872507
Guess it's caused by `create-react-app-typescript`/`react-scripts-ts` https://github.com/wmonk/create-react-app-typescript/issues/390
@wanttofly88 It is still an issue. I really recommend using those battle tested and feature-complete custom-elements V1 polyfills provided by WebReflection: - [`document-register-element`](https://github.com/WebReflection/document-register-element), don't be confused by it's name it...
@emilio-martinez I can't tell where this project goes. I just can tell, I used this project before, had this `built-in` issue and found those polyfills by WebReflection. So I compared...
Thanks for your reply. > Safari is dead-set against it I know, what a bummer... Anyway regarding a polyfill I would not follow a non-spec-compliant decision made by Safari. >...
Since `2.3.0` Jest throws **TypeError: The custom element constructor's prototype is not an object.**: From my insights it seems that two **different** `Object` constructors are being used, which causes this...
@mrsum Yeah it is WIP, actuallyI'm not certain [if it got abandoned](https://github.com/egoist/rollup-loader/issues/1) in favour of webpack 2. Anyway function marks will fail with treeshaking approach.
@idok Any updates on this?