André Mendonça

I think the problem is with the dependency "railsless-deploy" with the Cap3 ``` $ cap deploy undefined method 'instance' for Capistrano::Configuration:Class /Users/../.rvm/gems/ruby-1.9.3-p484/gems/railsless-deploy-1.1.3/lib/railsless-deploy.rb:1:in '' /Users/../.rvm/gems/ruby-1.9.3-p484/gems/capistrano-node-deploy-1.2.13/lib/capistrano/node-deploy.rb:2:in '' ```

@terox yes, it's incompatible because of railsless-deploy. To run it with success you will need to use Capistrano 2.x (until we fix it)

Note at railsless-deploy: "Capistrano 3 (http://www.capistranorb.com/) doesn't ship with any Railsisms, and is better in almost every measurable way than Capistrano 2 + raileless-deploy. It's time to switch, as I...

there is a discussion about this at https://github.com/vercel/next.js/discussions/39377 as well

I had a similar issue with App router only code. My workaround was to force 404 page based on the pathname: ```tsx // middleware.ts import { NextResponse } from 'next/server'...

I'm getting the same issue when the page has a `loading.tsx` (which adds a `` in the background).

> Like @andremendonca, I use page streaming and I get this random error when I call `notFound()` > > Disabling streaming (deleting `loading.tsx` file) fixes the issue Exactly what I...