-
Many analysis tools will use JSDoc tags to determine what web component specific features. To keep from fragmenting the ecosystem around different sets of JSDoc, we should make a recommended set of ta…
-
**Checklist**
- [x] Did you run the analyzer with the `--dev` flag to get more information?
- [x] Did you create a **minimal** reproduction in the [playground](https://custom-elements-manifest.netli…
-
Hi all-
I took a look through the docs and didnt see anything like this, so I figured I'd request it.
I think it would be really useful to support a option/flag in the `to-markdown` package and …
-
Hey team :wink:,
## Context
I'm still using the `_` prefix convention for private properties and methods. I know `#` is coming but I don't want to transpile and while I wait for better support, …
-
We should standardize on a package.json field to use to point to a custom elements manifest. This is important for indexers and catalogs that might need to inspect npm package for custom elements. The…
-
**Checklist**
- [x] Did you run the analyzer with the `--dev` flag to get more information?
- [x] Did you create a **minimal** reproduction in the [playground](https://custom-elements-manifest.netli…
-
Hey, I saw this list of supported jsdoc "tags"...
https://github.com/webcomponents/custom-elements-manifest/issues/42#issuecomment-778629278
would it be possible to allow extraction of custom ta…
-
"custom-elements.json" is a filename and not necessarily a description of the file's contents or purpose. The file specific name also might not be required to be `custom-elements.json`. On npm it coul…