Milan Raj

I think that would make sense if it is necessary to function. If someone pulls in components from two different component packages that pinned to different foundation versions would that...

Alternate wording of my previous comment: Forcing peerDependencies when it is not needed causes more potential headache for me. I have to resolve the peerDependency by fixing up package versions...

A more concrete example, say my app has the following dependencies: Without peerDeps, the following builds fine (assuming multiple copies of fe won't break my app): ``` fluent { deps:...

Is there a reason FF, et. al, in main is not using more normal semver specifiers like the archives branch instead of pinned? https://github.com/microsoft/fast/blob/c64110d2f1dfbc24a0978c362bcf72b8958e6d73/packages/web-components/fast-foundation/package.json#L98 Is it an artifact of the...

Actually I'll concede. It's unlikely most apps will need to leverage fast element / fast foundation based components from multiple disparate component library implementations. I'm not aware of any other...

Some thoughts: - I don't know if it is captured explicitly, but conceptually my mental model of fast foundation is that the components should align well with the browser native...

> > My reason for holding with button thus far is that I don't think the actual semantics of the button change, nor does it's form association behavior from what...

We have been using FoundationSwitch with a custom template to support the aria-pressed/read-only/disabled attributes (and start + end templates) for a couple years as a reference: https://github.com/ni/nimble/tree/main/packages/nimble-components/src/toggle-button Would still love...

Looks like the [tests only cover Data and not Vector](https://github.com/geoarrow/geoarrow-js/blob/75d35765cb1552be0f5562b35055f0b84ad1fa68/tests/worker/transfer.test.ts#L9), maybe an issue has been introduced? It does look like `preparePostMessage(Data)` and `rehydrateData` are working but the vector example shown...

@kylebarron This PR fixes the imports of the README example, but it looks like the README example still has other issues, see: https://github.com/geoarrow/geoarrow-js/issues/25