How to call custom middleware in this example

[kennyth01]

Hi all,
I have this script that calls sessionMiddleware:

import { sessionMiddleware, CookieStore, Session } from 'hono-sessions'

const app = new Hono<{ Bindings: Env, Variables: {
    session: Session,
    session_key_rotation: boolean
} }>()
const store = new CookieStore()

app.use('*', 
sessionMiddleware({
    store,
    encryptionKey: 'some_string_thritytwo_characters',
    expireAfterSeconds: 900,
    cookieOptions: {
      sameSite: 'Lax',
      path: '/',
      httpOnly: true,
    },
  }),
    async (c, next) => {
    console.log(`inside all [${c.req.method}] ${c.req.url}`)

    await next()
  })

This is working perfectly!

However, I want it to call inside the method like this so I can get the Context object

app.use('*',  async (c, next) => {
    console.log(`inside all [${c.req.method}] ${c.req.url}`)
sessionMiddleware({
    store,
    encryptionKey: c.env.MY_KEY,
    expireAfterSeconds: 900,
    cookieOptions: {
      sameSite: 'Lax',
      path: '/',
      httpOnly: true,
    },
  })
    await next()
  })

What is the correct way? The second snippet is not working correctly.

[NicoPlyley]

Are you looking to get access to the context inside your custom middleware?

Is so the context is passed to custom middleware but it does not have type safety. You can use the createMiddleware wrapper function which will add types to the context.

[kennyth01]

hi @NicoPlyley , Unfortunately, I'm not using custom middleware, I am using a 3rd party middleware called sessionMiddleware from hono-sessions

Yes, I want to get the context.

[NicoPlyley]

Where it is coming from in the first place, the only way I see is moving it to another location

[kennyth01]

What do u mean where is it coming from? Are you referring to this: c.env.MY_KEY

If yes, it'll be something like:

export type Env = {
    DATABASE_URL: string
    MY_KEY: string
}
const app = new Hono<{ Bindings: Env, Variables: {
    session: Session,
    session_key_rotation: boolean
} }>()
const store = new CookieStore()

app.use('*',  async (c, next) => {
    console.log(`inside all [${c.req.method}] ${c.req.url}`)
sessionMiddleware({
    store,
    encryptionKey: c.env.MY_KEY,
    expireAfterSeconds: 900,
    cookieOptions: {
      sameSite: 'Lax',
      path: '/',
      httpOnly: true,
    },
  })
    await next()
  })

[NicoPlyley]

Are you using CloudFlare Workers where you can only access env var in the context? If so, I would open an issue for hono-sessions to allow c.env names, in a parameter like encryptionKeyFromCtx. If you want a hacky way to make it work. Create a empty let out side any function to scope it globally. Make a middleware that saves the ctx env to that let. Then use that variable in the next middleware for the session

Very unconventional, but it should work. Ultimately this would be an issue on hono-sessions side.

[kennyth01]

thanks @NicoPlyley ,

I've manage to make it work via the following way:

export const cookieSessionMiddleware = async (c: Context, next: undefined) => {
    const store = new CookieStore()

    const m = sessionMiddleware({
        store,
        encryptionKey: c.env.SESSION_ENCRYPTION_KEY,
        expireAfterSeconds: 900,
        cookieOptions: {
          sameSite: 'Lax',
          path: '/',
          httpOnly: true,
        },
      })

      return m(c, next)
  }

then use this middleware:

app
.use('*')
.use(cookieSessionMiddleware)

[NicoPlyley]

Well glad that works you can use the createMiddleware to gives types to the context and next