Lambda Context callbackWaitsForEmptyEventLoop

[masterbater]

callbackWaitsForEmptyEventLoop does this exist in lambda context, its untyped

Is this correct ? is there any better way to load or initiate database connection in lambda

app.use("*", async (c, next) => {
  const { DATABASE_URL } = env<{ DATABASE_URL: string }>(c);

  const lambdaContext = c.env?.requestContext;
  if (lambdaContext) {
    lambdaContext.callbackWaitsForEmptyEventLoop = false;
  }
  await next();
});

Reference
https://mongoosejs.com/docs/lambda.html

[yusukebe]

cc: @watany-dev

[watany-dev]

The requestContext refers to the common event.requestContext in Lambda. It might be resolved by providing c.env.lambdaContext in the following PR.

#1523

  app.get('/lambda-context', (c) => {
    const fnctx = c.env.lambdaContext
    console.log(fnctx..callbackWaitsForEmptyEventLoop)
    return c.json(fnctx)
  })

Although not directly related to this topic, the current access to requestContext can be confusing. I feel it would be preferable to bind the lambdaEvent and access it via c.env.lambdaEvent.requestContext.