Custom Node Server Entry

[rtritto]

The #38 was merged and introduced from @photonjs/hono >= 0.1.7 (related vike-photon >= 0.1.17).
The serve function from @photonjs/hono was changed and it doesn't start the server because of https://github.com/photon-js/photon/blob/2592cac6476ef17d0811f5f210b39407e6a8750e/packages/runtime/src/serve.ts .

What is the best way to start a custom server entry?

Code

/server/index.ts

import { Hono } from 'hono'
import { apply, serve } from '@photonjs/hono'

const port = +(process.env.PORT || 3000)

function startServer() {
  const app = new Hono()

  apply(app)

  return serve(app, { port })
}

export default startServer()

Draft

import { createServer } from "node:http"
import serverStarted from '/server/index.ts'

const { port } = serverEntry.server!.options!

const server = createServer(serverEntry.server!.nodeHandler!)

server.listen(port, () => {
  console.log(`Server running at http://localhost:${port}`)
})

Going to http://localhost:3000, I have no response, probably the issue is with nodeHandler.

Related

• The requested module '../dist/server/index.mjs' does not provide an export named 'default' #49
• Rollup failed to resolve import "virtual:photon:resolve-from-photon:@universal-middleware/vercel/node/servers" #53 (comment)
• Server Emit Entry option vikejs/vike-photon#41

[anntnzrb]

After @photonjs/hono >= 0.1.7, serve() returns a ServeReturn object instead of starting the server directly. The server is now started by @photonjs/runtime/serve.ts. Simply export the result from serve(): export default serve(app, { port }) - do NOT manually call startServer() or extract nodeHandler.

[rtritto]

Thanks for the answer, you are right.
The fix of the issue vikejs/vike-photon#41 will achieve my use case:
Vercel with exports in server entry (no server start) and Docker (node server start).

E.g.:

/pages/+config.ts

...

export default {
  photon: {
    emitEntry: process.env.NODE_ENTRY === 'true'
  }
}