Generate Custom Elements Manifests from TypeScript sources

custom-elements custom-elements-manifest go golang static-analysis typescript web-components
3 Open Issues Need Help Last updated: Jul 3, 2025

Open Issues Need Help

View All on GitHub

AI Summary: The task is to fix a bug in the `cem generate` command where the `--output` flag's path is not resolved relative to the `--project-dir` flag, as it should be. The solution involves modifying the Go code to correctly join the project directory and output file path before writing the output file.

Complexity: 3/5
bug good first issue

Generate Custom Elements Manifests from TypeScript sources

Go
#custom-elements#custom-elements-manifest#go#golang#static-analysis#typescript#web-components
`cem get` 2 months ago

AI Summary: Implement a `cem get` command that retrieves specific custom element information (tag, module details, raw manifest data) given a package name and path, and optionally suggests alternative queries using Levenshtein distance. The command should also support a `--package` specifier.

Complexity: 4/5
enhancement good first issue

Generate Custom Elements Manifests from TypeScript sources

Go
#custom-elements#custom-elements-manifest#go#golang#static-analysis#typescript#web-components

AI Summary: Implement a `cem validate` command that checks a Custom Elements Manifest JSON file against the schema at https://github.com/webcomponents/custom-elements-manifest/blob/main/schema.json, considering the schema version in the manifest. The command should also provide optional warnings for lifecycle methods, static styles, and private members.

Complexity: 4/5
enhancement good first issue

Generate Custom Elements Manifests from TypeScript sources

Go
#custom-elements#custom-elements-manifest#go#golang#static-analysis#typescript#web-components