[BUG] Error: Could not find the node's symbol.
See original GitHub issueOverview of the issue
After upgrading to compodoc 1.1.1 from 1.0.9 I got the reason: Error: Could not find the node's symbol.
error
Operating System, Node.js, npm, compodoc version(s)
compodoc: 1.1.1 node: 9.8.0 mac: High Sierra
Angular configuration, a package.json
file in the root folder
Angular: 5.2.9
Compodoc installed globally or locally ?
locally installed compodoc
Motivation for or Use Case
Cannot generate docs anymore
Reproduce the error
npm script:
./node_modules/.bin/compodoc -p src/tsconfig.app.json -d ./docs -t --theme stripe --disableCoverage --hideGenerator -n \"My Documentation\"
Related issues
1.0.9 compodoc version was working well
Suggest a Fix
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:40 (7 by maintainers)
Top Results From Across the Web
Troubleshooting - Puppeteer
The most common cause is a bug in Node.js v14.0.0 which broke extract-zip , the module Puppeteer uses to extract browser downloads into...
Read more >Could not find a node for attributes {'bmc_address': None, 'mac'
Previously, an issue in the logging prevented introspection from functioning correctly. As a result, introspection failed when the hardware ...
Read more >Node.js v19.3.0 Documentation
If the function does not return a promise, assert.doesNotReject() will return a rejected Promise with an ERR_INVALID_RETURN_VALUE error. In both cases the error...
Read more >Troubleshooting errors in AWS Glue
First check if an error is listed in the AWS Glue console crawlers list. Check if there is an exclamation icon next to...
Read more >FAQ - Graphviz
If you cannot find the answer to your question here, ask it in the ... In the diagram below, the shaded nodes will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am currently seeing this issue as well when routes are being analyzed. This is the initial output of the error:
I believe that this is happening due to our usage of a TS string enumeration to define the
path
of the individual routes. For example: (redacting portions of the config)Enum file:
Routing Module Config:
Not ideal but I got this working by removing the Routes typing, example :
export coreRoutes : Routes = [ ... ]
Change to
export coreRoutes = [ ... ]