Steve Workman

@stevegal I asked Solis for the API this morning and I was not asked to sign an NDA. The docs are on their OSS server. - API https://oss.soliscloud.com/doc/SolisCloud%20Device%20Control%20API%20V2.0.pdf - List...

I contacted Solis support through their official channels and the above was what I got > What email pls. is only think stopping me from using it 😊 Refuse to...

+1 from the Maersk Design System team too

I believe we can make it a little better by doing something like this ```ts attachPropsToRenderer(): void { const customElementConstructor = getCustomElementConstructor(this.litElementTagName); const props = this.litElementVnode.props; if (props && this.renderer)...

> I don't think the `typeof` check is necessarily the right thing. Rather, if the key is not `in` the element prototype, it's not something the element is expecting to...

I've added a test component based on one we have at Maersk that is showing the hydration and SSR issue in https://github.com/prashantpalikhe/nuxt-ssr-lit/pull/35 (my-step-indicator). The outer component, which was wrapped in...

@augustjk yes, in this case `labels` is `[]` client-side - it's passing through perfectly well server-side. Changing the property to a string and splitting it with commas works without any...

Yes, fixed in 3.4.36

With the great suggestions above I think we're a few steps closer - however, we still get the hydration issue described in #34

When combined with the latest Lit fixes, and https://github.com/vuejs/core/pull/7300 - this works properly in dev mode. The key was that Nuxt does not set the compiler options in runtime, so...