Evan Slawski

Are there any considerations we need to make for our React wrapper components?

Learned today that modules shared via ModuleFederation are unable to be tree shaken. So it's worth noting that if we go this route the entirety of the `@ithaka/pharos` module will...

Sounds like a reasonable enhancement. It does feel like this would be a breaking change if we are removing a component and changing behavior. Even if we aren't leveraging it...

I agree that option (2) seems like the lesser of all evils at this juncture. Assuming we will want to release this in a major version as it will be...

> > Assuming we will want to release this in a major version as it will be a breaking change for anyone using the existing implementation of table component. >...

> Here is [a relevant passage from the Lit documentation](https://lit.dev/docs/components/defining/#typescript-typings) about providing good TypeScript typings as well. I’m not quite sure this addresses what we need. The TypeScript type in...

> [@eslawski](https://github.com/eslawski) because React binds DOM properties, it's possible you don't actually need that conversion and can indeed use the camelCase flavor (I haven't tried this). I'd be interested if...