7 replies

Difference in Finalizer Execution Timing Between Bun and Node.js

there's a difference of behaviour between bun and node here:

      HttpRouter.get(
        "/test",
        Effect.gen(function*() {
          yield* Effect.addFinalizer(() => Effect.sync(() => console.log("Test endpoint finalized")))
          console.log("Test endpoint reached")
          return HttpServerResponse.stream(Stream.never)
        })
      )

      HttpRouter.get(
        "/test",
        Effect.gen(function*() {
          yield* Effect.addFinalizer(() => Effect.sync(() => console.log("Test endpoint finalized")))
          console.log("Test endpoint reached")
          return HttpServerResponse.stream(Stream.never)
        })
      )

      HttpRouter.get(
        "/test",
        Effect.gen(function*() {
          yield* Effect.addFinalizer(() => Effect.sync(() => console.log("Test endpoint finalized")))
          console.log("Test endpoint reached")
          return HttpServerResponse.stream(Stream.never)
        })
      )

      HttpRouter.get(
        "/test",
        Effect.gen(function*() {
          yield* Effect.addFinalizer(() => Effect.sync(() => console.log("Test endpoint finalized")))
          console.log("Test endpoint reached")
          return HttpServerResponse.stream(Stream.never)
        })
      )

visiting that route will print test endpoint finalized immediately in console on Bun,
and on Node only once the user disconnects (as expected).

can only be reproduced with stream. classic response (sleep 5s, then return a HttpServerResponse.text) does not exhibit the issue.

Difference in Finalizer Execution Timing Between Bun and Node.js

Similar Threads

Similar Threads

Similar Threads