default hotreload of nextjs error

[lileilei]

The nodemon experience was poor！！！

[kyle-mccarthy]

Hi, this is indicative of the Render filter not being set up correctly. Did you just clone the repo and have this happen or were you migrating it into an existing project? I converted this into a NPM package which makes the set up more straight forward. You can see the package repo here https://github.com/kyle-mccarthy/nest-next and then this is the actual package https://www.npmjs.com/package/nest-next

PS this is what you should be seeing!

[lileilei]

Thank you for your answer, I've configured it. Can it be used in production environment ?

and I find the default SPA of Nextjs invalid. When I switch pages，One more list.js request,I guess it's because of the default configuration of next. Js.This should be a single page application

[kyle-mccarthy]

I am using this in production and haven't had any issues. However, I would highly recommend using the nest-next package so if I do discover anything you can easily update it rather than making the changes to your local render files.

And that is interesting, are you using the the Link component from next/link to handle the routing between pages? Also does that happen when you make a change to the page or just when you route?

Assuming that those requests are sorted in the order that they were made, I find it odd that there would be a request to the List.js file prior to the main document request.