You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am working on a new cem-plugin using a fork of the cem-plugin-template provided here (thanks for this template btw!)
I noticed some odd behavior between versions 0.5.5 and 0.5.6 of the analyzer plugin. I'm hoping you can offer some clarification on the differences between these versions and what I can do to test my plugin against the latest version of the analyzer.
The behavior is observed with the unchanged plugin template files.
I install "@custom-elements-manifest/analyzer": "0.5.5", and run the analyzer on my file using the start script. analyzePhase prints 305 SourceFile for the root node of the source and continues to each of the node's children.
My plugin works as expected with this version and produces the "correct" custom-elements.json.
I bump the package version to "@custom-elements-manifest/analyzer": "0.5.6",, install, and re-run the analyzer on my file. analyzePhase prints 305 JSDocUnknownType for the root node and fails to continue to any children. The subsequent custom-elements.json file contains no declarations nor exports.
Isn't the analyzePhase function supposed to iterate over each node in the AST?
Is there a change I should make to the template to make the plugin behave in this way?
Thanks for any help you can provide!
The text was updated successfully, but these errors were encountered:
au-z
changed the title
cem-plugin-template - 'SourceFile' becomes 'JsDocUnknownType' in 0.5.6
cem-plugin-template: 'SourceFile' becomes 'JsDocUnknownType' in analyzer >= 0.5.6
Jul 21, 2022
Hi, I am working on a new cem-plugin using a fork of the cem-plugin-template provided here (thanks for this template btw!)
I noticed some odd behavior between versions 0.5.5 and 0.5.6 of the analyzer plugin. I'm hoping you can offer some clarification on the differences between these versions and what I can do to test my plugin against the latest version of the analyzer.
The behavior is observed with the unchanged plugin template files.
I install
"@custom-elements-manifest/analyzer": "0.5.5",
and run the analyzer on my file using thestart
script.analyzePhase
prints305 SourceFile
for the root node of the source and continues to each of the node's children.My plugin works as expected with this version and produces the "correct" custom-elements.json.
I bump the package version to
"@custom-elements-manifest/analyzer": "0.5.6",
, install, and re-run the analyzer on my file.analyzePhase
prints305 JSDocUnknownType
for the root node and fails to continue to any children. The subsequent custom-elements.json file contains no declarations nor exports.Isn't the analyzePhase function supposed to iterate over each node in the AST?
Is there a change I should make to the template to make the plugin behave in this way?
Thanks for any help you can provide!
The text was updated successfully, but these errors were encountered: