Calling CreateServer (/next/dist/server/next.d.ts) cannot return NextServer object after 13.4.3

[raychunghk]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Next.js 13.4.3 and newer
Nest.js 10

Which example does this report relate to?

n/a

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

My project is setup with nest.js 10, next.js, and bridged with nest-next.
In this function imports

    RenderModule.forRootAsync(
       Next({ dev: true }),
      /* null means that nest-next 
                should look for pages in root dir */
      { passthrough404: true, viewsDir: null },
    
    ),

inside below, The Next({ dev: true }) param is good because it is able to return a NextServer object in the file:
/node_modules/next/dist/server/next.d.ts
But this is not after version next 13.4.3

imports: [
    RenderModule.forRootAsync(
       Next({ dev: true }),
      /* null means that nest-next 
                should look for pages in root dir */
      { passthrough404: true, viewsDir: null },
    
    ),
    StaffModule,
    TestModule,
    TimesheetModule,
    LeaveRequestModule,
    VacationsModule,
    AuthModule,
    TypeGraphQLModule.forRoot({
      driver: ApolloDriver,
      emitSchemaFile: true,
      validate: false,
      path: '/absproxy/5000/graphql'
      , authChecker: ({ context }, roles) => {
        return true;
      },
  
    }), RecipeModule,
  ],
  controllers: [AppController],

  providers: [AppService, UserResolver, PrismaService],
})
export class AppModule { }

Expected Behavior

The CreateServer function inside should return a NextServer object.
/config/workspace/vm/js/NxTime/node_modules/next/dist/server/next.d.ts

To Reproduce

Create a empty nest project

$ npm i -g @nestjs/cli
$ nest new project-name

add Next.js 13.4.2 in the project

 npm install next react react-dom

In the main.ts, import Next and log the object by calling "Next" like below

import Next from 'next';
async function bootstrap() {
 
  const app =   Next({ dev: true })
  app.prepare();
  console.log(app)
}

With Next version: 13.4.2 or lower, the above log will report

NextServer {
  options: { dev: true },
  serverPromise: Promise {
    <pending>,
    [Symbol(async_id_symbol)]: 41,
    [Symbol(trigger_async_id_symbol)]: 37
  }
}

With Next version >=13.4.3
the app object is logged as {}

[tunatoksoz]

I believe this is the place things changed

next.js/packages/next/src/server/next.ts

Line 281 in 5e36c34

get: function (_, propKey) {

Presumably changed after this difF:
c7e5d76

[lluiscab]

Taking a look at the current status of this issue, it all seems to be related to whatever or not the customServer property is set when initializing a NextServer instance. When this value is set to true (or more specifically, not explicitly set to false), then instead of getting an instance of NextServer we get a Proxy that limits the access we have to NextServer properties.

The following code change fixes this issue:

diff --git a/packages/next/src/server/next.ts b/packages/next/src/server/next.ts
index fabcea9..b6416ef 100644
--- a/packages/next/src/server/next.ts
+++ b/packages/next/src/server/next.ts
@@ -413,10 +413,16 @@ function createServer(options: NextServerOptions): NextServer {
               }
             }
             default: {
-              const method = server[propKey as keyof NextServer]
-              if (typeof method === 'function') {
-                return method.bind(server)
+              const methodOrProperty = server[propKey as keyof NextServer]
+              if (typeof methodOrProperty === 'function') {
+                return methodOrProperty.bind(server)
               }

+              return methodOrProperty
             }
           }
         },

Unfortunately, this change isn't enough, the proxy overrides the prepare() function and it's current implementation does not set the properties we're interested on (app.server (see https://github.com/kyle-mccarthy/nest-next/blob/master/lib/render.module.ts#L31) & app.dynamicRoutes (see https://github.com/kyle-mccarthy/nest-next/blob/master/lib/render.module.ts#L37) ).

Could we get some input from a project maintainer such as @shuding or @ijjk? (both have recently modified this file, and @shuding introduced the proxy return)

[razyalov]

Is there any movement on this issue? Did anyone find a solution to this problem?

[sergeysportcore]

Any updates?

[kaminion]

It's going on, it's forcing to use low version