Cannot render page with path "\index", did you mean "/\index"?
See original GitHub issueDescribe the bug
I tried all the methods and when I tried to run yarn start: dev
, I got the following error but I could not find any solution.
Cannot render page with path "\index", did you mean "/\index"?. See more info here: https://nextjs.org/docs/messages/render-no-starting-slash
I used any kind of educational article, I went all the way correctly but this bug was in front of my eyes.
Expected behavior I expected the index path to be rendered successfully but 404 was executed and more importantly the above error is displayed to me on the console
Repository URL: https://github.com/mmdzov/nest-next-monorepo
Version
- next.js: 12.0.8
- nest: 8.1.1
- nest-next: 9.5.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unable to render index.html file from my view folder in angular2
I want that when I run npm start command in /client folder it should render index.html file from /views folder, what I'm doing...
Read more >404 errors with dynamic routes in next.js and now · Issue #3294
Error seems to occur because there isn't a index.js entry point like how we handle a create react app. It has nothing got...
Read more >Dynamic Routes Details - Next.js
Here is some essential information you should know about dynamic routes. ... path will serve the generated page, just like other pages pre-rendered...
Read more >Ultimate React Router v6 Guide
All this is saying is that the path of the index Route is the same as the parent Route . Now if this...
Read more >Error 404 Guide for SEO & Usability (FAQs & More)
How do you vet and prioritize 404s - and other HTTP status errors - for fixing? How do you QA a 404 page?...
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
Hi @mmdzov I published a new version with a fix for this!
I executed it and the output was
/path/to/file