Hubert SABLONNIÈRE

@whitlockjc Fair enough, thanks very much.

I wanted to explain this format to my intern and yes, having some examples and docs would be awesome. Is this something that should be on webcomponents.org v2?

I don't have a strong preference for any of 1, 2 or 3. We've been listing a few custom stuffs in our components' JSDoc so we could see them in...

I share the concern about this manifest becoming a mess but in my use cases, it makes sense to rely on the existing analyzer to extract the custom info. It...

Thinking about OpenAPI spec, they allow for extensions with a `X-` prefix. I'm not saying it's perfect but it's an option. Look at this doc https://swagger.io/specification/ under "Specification Extensions".

I have a map component and 2 marker components that expose 3 readonly properties, I used to annotate them like this: ```js /** @readonly */ this.size = [16, 16]; /**...

I decided to move those to getters (without setters) and I'll create a CEM analyzer plugin that used this "getter but no setter" to identify fields as readonly.

> I think we should support cases where the manifest is not necessarily associated w/ a package.json I think so too. If we take the devtools addon @matsuuu is working...

You mean an icon for the whole component library referenced by the CEM?

We also stumbled upon this behaviour and we were expecting `this` to be bound to the custom element.