Justin Fagnani

@blois How hard would it be to add [[ ]] expressions to the Angular transformer?

Is there a way to plug into the the extractor? This same work got rejected from Angular core, so I would expect changes to the extractor to be too. The...

@zoechi Angular's web component support design will not currently work with many of the custom elements in core-\* and paper-\* because they don't fire 'change' events when properties change. I...

Ouch, Angualr's expression extraction support is very limited, making this issue impossible to fix right now. Basically Angular's extractor supports `{{ }}` expressions, or directives can declare in their annotation...

The CSS tag utilities have no overlap with lit-html's responsibilities though. lit-html doesn't do anything with either CSS or shadow roots.

That use seems great though. That module is not going to pull in anything else from reactive-element. The only thing that would be saved by a separate lit/css package is...

Do they have to know? Can you just re-export the `css` tag from your library?

You shouldn't need React-specific libraries for deep equals. Just a visited object set to keep from entering cycles.

Thanks @jun-sheaf! We need a changeset file as part of the PR. See https://github.com/lit/lit/blob/main/CONTRIBUTING.md#pull-requests

I have a utility that deals in a single signal and needs to peek it. Having a `Signal.subtle.peek(signal)` function would be great for that.