Kyle McCarthy

I actually don't have any experience with using HMR along with nest. If you resolve this issue, I would appreciate it if you could provide a solution for any future...

So I haven't actually tried this before, but messed around and think I found a solution. You will want to create your own global ExceptionFilter that passes the request and...

Could you try updating the code for that filter to call the request handler like `return this.requestHandler(req, res);`. I noticed a problem with the query not being what next was...

ah yeah, I forgot that fastify modifies the req and res. I believe that you can also do ``` return this.requestHandler(req.raw, res.res) ```` That is how we handled it in...

@jgoux I think that should be possible. Just to clarify, you want all the requests that Nest thinks are 404s to be handled by Next's request handler? The only problem...

@jgoux Oh yeah so this issue is a little older and uses the deprecated bootstrapping method - you don't need to call it in your bootstrap file anymore. See https://github.com/kyle-mccarthy/nest-next/blob/master/examples/basic/src/main.ts...

That is correct, since you need to provide the RenderService for your filter. And I don't really see any issue with passing the request to next when nest 404s, I...

@jgoux @dayrim I've made the updates that will allow for you passthrough requests that 404 to next. It's currently on the [next branch](https://github.com/kyle-mccarthy/nest-next/tree/next) and you can preview it by doing...

@jgoux I actually think that should be possible by omitting step 1 from my previous comment. The only reason I actually did that is so that next knows it should...

@jgoux Did you have an opportunity to try this out? If it works for your use case, I can merge this and deploy a new version.