Joe Pea

Or a related note, is there a guide on how to add type definitions for any non-Lit elements so that Lit users have the full type safety in Lit templates?

This is lit-specific. We need something where libraries can easily map types of their library elements to types the `html` templates accept, etc. For example, for [Solid.js](https://solidjs.com/) `html` templates, we...

The other error that also appears in the console is reported in https://github.com/webcomponents/shadydom/issues/207.

@ljharb perhaps this is more surprising: ```js class MyElement { // define this first static #computeFoo() { return 'foo'; } @computed(MyElement.#computeFoo()) // still error! accessor foo; } ``` Humorously, this...

The fact that we can read the method (without calling it) in Babel is strong evidence that this can be made to work with all of the existing semantics. I...

The awesome thing about source order would be the author gets to decide, rather than a seemingly-arbitrary spec rule. If source order were first class, then if something would need...

> ### But decorators violate that expectation Fully agreed. This is very awkward. > they are asking for something that the language _already allows_ in every non-decorator context. Very good...

I agree the rationale for current orderings is [not](https://github.com/tc39/proposal-decorators/issues/571) [necessarily](https://github.com/tc39/proposal-decorators/issues/566) [intuitive](https://github.com/tc39/proposal-decorators/issues/565), however `acessor`s create _prototype_ descriptors, which _must_ already exist after the class is defined (before any instance is ever...


> I'm trying to understand how React and Vue can report 100% compatibility. Yeah, definitely. The tests are not covering everything they need to cover. This issue is a subset...