Thanks Burton! Definitely agree.

👋🏼 over here!

You don't have to - stencil will generate a types file itself if you set the option in the config. But for consistency with our existing setup I've been adding the extra step in a custom script.

Currently only outputting for React, so can only speak to that, but Stencil can generate a types file when it builds components. We wanted individual types files per component in our React library so I wrote a script to generate these after Stencil builds and added them to the wrapper. Works well.

There's definitely an element of that in there too 😅 but there's a lot of Stencil specific stuff that I've had to just trial & error to find the right solution.

Exactly! The irony being that not all products use React, but seems the suggestion is they should "just all start using React instead". 🤦‍♀️
(I'm just gunna keep building them as we've planned until we're told not to... Who cares how they were made if they work the same?)

If you're getting React components at the end of it, why does it matter how they were built? Not to mention the long term future proofing benefits we get from web-components. Urghhh 😣

💯
I'm on a team building a Design System for products using multiple frameworks, which we can cater for on the web side using web-components, but my current thinking is a mobile library will need to be a completely separate entity. There's only so far you can go with framework agnostic code.

I'm worried that this might be the case... Luckily I have a lot of React experience so can spot the bs, but if it comes down to who can shout louder, I'm concerned they're going to win.

Hmm interesting!
The only explanation I can think of in this case is it's someone getting overly enthused about react-native-web, but as our product is predominantly web based (with a supporting mobile app) it seems wild to move to a framework built for mobile app development.

I've previously had to build a web app using React Native and it's not a straightforward experience, I don't see why this would become the standard.
#React #ReactNative #ReactDevelopers #webcomponents