question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Route Page Exception

See original GitHub issue
Overview of the issue

Generated Routes pages does not render any routes.
No error messages during generation. Other pages working correctly.

Open Chrome Debugger, see the following:

prism.js:14 Uncaught TypeError: Cannot read property ‘toString’ of undefined at prism.js:14 at prism.js:14 (anonymous) @ prism.js:14 (anonymous) @ prism.js:14 d3.v3.min.js:2 Uncaught TypeError: e.sort is not a function at d3.v3.min.js:2 at ui (d3.v3.min.js:2) at n (d3.v3.min.js:2) at HTMLDocument.<anonymous> (routes.js:37)

Operating System, Node.js, npm, compodoc version(s)

Windows 10 Node 6.11.4 Compodoc 1.1.2

Angular configuration, a package.json file in the root folder

Attached package.json.txt

Compodoc installed globally or locally ?

Globally installed compodoc

Motivation for or Use Case

We love compodoc, but desperately need to see the routing graph to

Reproduce the error

Routes_index.js as generated attached (plus pretty printed) routes_index.js.txt

Related issues

I see ‘similar’ issues, but have not been able to deduce the necessary changes (if it is our code). #216 ??

Suggest a Fix

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
vogloblinskycommented, Apr 13, 2018

Ok reproduced. The children routes, for example prototypeRoutes are dynamic references Compodoc need to handles too to have a complete reference of all the routes during the parsing.

0reactions
lock[bot]commented, Dec 6, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

Read more comments on GitHub >

github_iconTop Results From Across the Web

React Router Error - Cannot GET [Page Name] - Stack Overflow
I am following along with Wes Bos' video series but am hitting a snag when I try to access any route other than...
Read more >
Error boundary causes React Router links to stop working
If I tried to navigate to the /page-with-error route, I'd get the error screen because the page had a runtime error.
Read more >
Routing • Docs • SvelteKit
svelte and src/routes/+error.svelte before rendering the default error page. If that fails (or if the error was thrown from the load function of...
Read more >
errorElement v6.6.1 - React Router
When exceptions are thrown in loaders, actions, or component rendering, instead of the normal render path for your Routes ( <Route element> ),...
Read more >
Fixing the 'cannot GET /URL' error on refresh with React ...
The root of the issue is that you're relying entirely on client side routing without setting up any logic to handle server-side routing....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found