-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Using the analyzer without plugins works fine, but trying with the type-parser plugin does not:
PS C:\devel\wsdir\packages\our-webcomponents> npm run cem
> our-webcomponents@0.0.1 cem
> npx custom-elements-manifest analyze --config ./custom-elements-manifest.config.js
C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:13387
function getSourceTextOfNodeFromSourceFile(sourceFile, node, includeTrivia = false) {
^
RangeError: Maximum call stack size exceeded
at getSourceTextOfNodeFromSourceFile (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:13387:45)
at getTextOfNode (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:13407:12)
at declarationNameToString (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:13680:62)
at getNameOfSymbolAsWritten (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:54415:18)
at createAccessFromSymbolChain (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:52297:27)
at symbolToTypeNode (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:52274:28)
at typeReferenceToTypeNode (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:51391:30)
at typeToTypeNodeWorker (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:50905:85)
at typeToTypeNodeHelper (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:50749:26)
at typeReferenceToTypeNode (C:\devel\wsdir\node_modules\@custom-elements-manifest\analyzer\node_modules\typescript\lib\typescript.js:51326:33)
Node.js v22.16.0
npm error Lifecycle script `cem` failed with error:
npm error code 1
npm error path C:\devel\wsdir\packages\our-webcomponents
npm error workspace our-webcomponents@0.0.1
npm error location C:\devel\wsdir\packages\our-webcomponents
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c npx custom-elements-manifest analyze --config ./custom-elements-manifest.config.js
Maybe it's caused by the project directory being part of an npm workspace?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels