Augustine Kim

@jun-sheaf I am curious though, have you come across a situation where this kind of strict association of key type to the context object was needed? Maybe the problem is...

Wouldn't that require the static unwrapper to lookback and remove the attribute and whole value on `nothing`?

All the `lit/directive.js` exports on that page are showing `lit/async-directive.js` since I assume typedoc found it from that file first. Ideally, I think we could show both import sources, with...

I wasn't as involved at the creation of this package but I'd imagine omitting `/lib/` from package exports is intentional and things meant for end-user consumption are only exposed via...

Recent versions of `preact` include almost all compatible types that can replace those from `react`. See this issue reported in the lit repo: https://github.com/lit/lit/issues/4138#issuecomment-1702562940 This https://github.com/preactjs/preact/issues/4124 is the missing piece...

> 2. Drop the direct dependency of `@lit/reactive-element` from `lit` So we actually don't want to change our dependency graph as that will cause an additional waterfall of dependency request...

`@lit/[email protected]` was just released which includes the fix for this. Specifically the decorators need to come from the latest `@lit/reactive-element`, and it can then be applied to fields on classes...

Type refactor done in https://github.com/lit/lit/pull/4027 with current version of `preact/compat` make it so that wrapped components are compatible type-wise. #4111 adds a test Preact project into the repo to make...

Completed in https://github.com/lit/lit/pull/3467

Related https://github.com/lit/lit/issues/3902