Build error on nested routes configuration
See original GitHub issueGot the following error when run build with guess opt active
UnhandledPromiseRejectionWarning: TypeError: childrenArray.getChildren is not a function
at getRoute (C:\Users\<MY-PATH>\node_modules\guess-parser\dist\guess-parser\index.js:364:14)
It occurs only when I setup nested routes configuration:
- ‘administration’
- ‘second’
- ‘’
- ‘first’
- ‘’
- ‘**’
With routes at the same level:
- ‘second’
- ‘first’
- ‘’
- ‘**’
I don’t get any error.
Repo for reproducing the error: link
Build command: npm run build:guess
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
React-router: nested routes error - Stack Overflow
Can someone advise how to make the nested users routes work? I'm using webpack to bundle my jsx. Edit 1: I included my...
Read more >Generating nested routes while trailingSlash is true #8165
What is actually happening? The command is failing with error This page could not be found and missing trailing slashes on nested routes....
Read more >React Router 6 Tutorial #4 - Nested Routes - YouTube
Get access to premium courses on Net Ninja Pro:https://netninja.dev/courses My Udemy ...
Read more >The Power of Nested Routes in Remix - Matt Stobbs
Nested routing allows us to create layout components that are shared across multiple pages, but it also unlocks a lot more than that....
Read more >React Router: A simple tutorial on nested routes.
To create these nested routes, we will create one similar array of routes, as we have created above, but inside Home component.
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 can confirm this problem. I will try to dig in too.
@morganpizzini would you provide a minimal demo where I can reproduce the problem? Please open a new issue with it. Thanks!