Bun/Hono & Next.js Issues
I copied the counter actor quickstart from the bun / hono getting started.
and then used the react package on my nextjs project to test it out.
ran into a variety of issues.
1. originally used
2. then I get these errors in the nextjs console:
And on my server:
So for context, I've plugged this into an existing bun/hono server.
An oversimplified example of how im using my server:
any ideas what im getting wrong? Assumed it was because I wasnt using the default rivet 'serve' but figured mounting the /registry route solves that??
and then used the react package on my nextjs project to test it out.
ran into a variety of issues.
1. originally used
cors({ origin: "*" })cors({ origin: origin => origin ?? ' ',
credentials: true
})2. then I get these errors in the nextjs console:
POST http://localhost:8000/registry/actors/resolve 500 (Internal Server Error)level=ERROR msg=failed to resolve actor ID error=Error: Internal error. Read the actor logs for more details.WebSocket connection to 'ws://localhost:8000/registry/actors/connect/websocket' failed http-client-driver.ts:146 level=WARN msg="socket error"log.ts:53 level=WARN msg="socket closed" code=1006 reason="" wasClean=falselog.ts:53 level=WARN msg="failed to reconnect" attempt=2 error="Error: Closed"And on my server:
level=WARN msg="internal error" error="Failed to load actor state: Error: ENOENT: no such file or directory, open '/home/nicka/.local/share/rivetkit/server-.....'" stack="Error: Failed to load actor state: Error: ENOENT: no such file or directory, So for context, I've plugged this into an existing bun/hono server.
An oversimplified example of how im using my server:
const { client, hono, handler } = registry.createServer()
const hono = new Hono()
app.use(cors({
origin: origin => origin ?? ' ',
credentials: true
}))
app.onError(errorHandler)
app.notFound(notFoundHandler)
app.route('/registry', hono)
// example rivet endpoints for counter (omitted)
// other routes (omitted)
Bun.serve({
...options,
routes: staticRoutes,
fetch: (req, server) => {
const ip = server.requestIP(req);
return app.fetch(req, { ...env, ip, server });
},
})any ideas what im getting wrong? Assumed it was because I wasnt using the default rivet 'serve' but figured mounting the /registry route solves that??
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Was this page helpful?
