Dries

After some debugging I found out myself that's a limitation of web-component-analyzer parsing logic in [function `resolveNodeValue`](https://github.com/runem/web-component-analyzer/blob/35efadcd09391b720c4b0f4a2054c38d4287d57f/src/analyze/util/resolve-node-value.ts#L18) There's no support for nodes of type `PropertyDeclaration`. I'll make a change and...

I also found that lit-analyzer triggers _no-missing-element-type-definition_ for such cases. lit-analyzer uses function [discoverDefinitions](https://github.com/runem/web-component-analyzer/blob/master/src/analyze/flavors/custom-element/discover-definitions.ts#L13) which calls [getInterfaceKeys](https://github.com/runem/web-component-analyzer/blob/master/src/analyze/util/ast-util.ts#L185). If `PropertyDeclaration` is supported, it wil resolve the static class property found in...

Indeed, that combination seems to be working. (Using the latest TS at this moment, 5.4.5, results again in the same error)