Hannah Clarke
@hannahc.bsky.social
Design System UI Engineer
Music listening, photo taking, road tripping, app building, void staring.
(she/her)
Music listening, photo taking, road tripping, app building, void staring.
(she/her)
Thanks Burton! Definitely agree.
October 15, 2025 at 11:15 AM
Thanks Burton! Definitely agree.
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.
January 18, 2025 at 12:58 AM
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.
January 16, 2025 at 9:22 PM
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.
November 18, 2024 at 4:33 PM
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?)
(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?)
November 14, 2024 at 7:31 PM
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?)
(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 😣
November 14, 2024 at 2:34 PM
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 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.
October 11, 2024 at 12:25 PM
💯
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 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.
October 11, 2024 at 9:26 AM
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.