"push is not a function of null" about custom-elements-manifest HOT 6 CLOSED

Hmm, attempting to recreate this from a brand new component seems to not have this issue

I'm experiencing this with a monorepo where each component is being analyzed, ill have to look into this further myself as this might be an issue with my setup

will re-open if more detail can be given in future

from custom-elements-manifest.

Is the issue that you're analyzing polymer v3 components while using the --litelement flag?

from custom-elements-manifest.

I am analyzing lit components that have polymer v3 components as dependencies eg importing 'paper-input' into a Lit component

from custom-elements-manifest.

That shouldnt be a problem. Can you show me a minimal reproduction in the playground, and the fix you implemented privately so I can better understand what the problem is?

from custom-elements-manifest.

On further notice it looks like the config i had set for the analyzer wasnt quite correct and upon updating it has removed the issue

It was pulling in files containing parts i didnt need or want in the json generated anyway, updating the --globs flag did the trick

Apologies for the unnessary issue

from custom-elements-manifest.

No worries!

from custom-elements-manifest.