Justin Fagnani

Argh, another problem that Dart's two-pass constructor feature fixes. Thanks for pointing this out @jridgewell The only robust way I can think of avoiding this is to move the responsibility...

We definitely don't want to encourage testing in Jest because it's not a browser that any users use. We don't use Karma, but have updated starter kits to use `@web/test-runner`.

Thanks for looking into this @jridgewell ! The one thing I wonder about, if the global tree walker is the cause, is how that would show up as a leak...

I just noticed that this also breaks find-all-references, and that probably means that it beaks cross-package refactoring. The dev workflow hit here is pretty bad, IMO.

I just tried to use graphql-request with a `@web/dev-server` and it doesn't work because it's not published as modules.

Tagging myself, @kevinpschaaf and @augustjk here... Element-bindings are imperative only right now. In order for SSR to support them we'd need a declarative form - a value that an element...

We had difficulty implementing the spread semantics that we want within our code budget. One of the big issues is how to deal with key collisions within spread objects, especially...

@daKmoR if the polyfill supported something like that it should probably be hashed out as a WCCG community protocol. Some other utilities I've seen look for a static `tagName` or...

> "Use webpack for apps, and Rollup for libraries" I've heard this, but I don't think it's a useful convention. First, you just shouldn't bundle module-based packages at all. Second,...

I want to point out that declarative custom elements and declarative shadow DOM have no relation, except that declarative custom elements _must not_ use `` in the template definition, as...