dad living in Switzerland 🇨🇭 mainly working on typescript, css and compiler related frontend topics - maybe you know me from html-webpack-plugin, text-box-trim or next-yak
You are right it would be better if react would be able to deal with webcomponents out of the box
But there are different solution which build a bridge and allow to use webcomponents directly in react app e.g.: github.com/BBKolton/reactify-wc
constVaadinButton=reactifyWc("vaadin-button");
Facebook would also need to reactify webcomponents so the only difference is that this code would then be written by Facebook itself.. I am not sure why using another OOS package is such a big issue..
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You are right it would be better if
reactwould be able to deal with webcomponents out of the boxBut there are different solution which build a bridge and allow to use webcomponents directly in react app e.g.: github.com/BBKolton/reactify-wc
Facebook would also need to reactify webcomponents so the only difference is that this code would then be written by Facebook itself.. I am not sure why using another OOS package is such a big issue..