10 replies

Have a fun one for the Workers team...

Have a fun one for the Workers team... itty-router is staged to release as v5, but we're running into an issue with the direct export signature.

Background:
An itty

Router

Router

instance is a

Proxy

Proxy

, with a

fetch

fetch

method. This matches the expected

{ fetch }

{ fetch }

signature that Cloudflare or Bun expect. However, CF is having issues with the Proxy (Bun is fine with it, for comparison).

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

Cloudflare Developers•2y ago•

10 replies

Kevin

Have a fun one for the Workers team...

Have a fun one for the Workers team... itty-router is staged to release as v5, but we're running into an issue with the direct export signature.

Background:
An itty

Router

Router

instance is a

Proxy

Proxy

, with a

fetch

fetch

method. This matches the expected

{ fetch }

{ fetch }

signature that Cloudflare or Bun expect. However, CF is having issues with the Proxy (Bun is fine with it, for comparison).

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

const router = Router()

// doesn't work (but should)
export default router

// works
export default {
  fetch: router.fetch
}

// works
export default { ...router }

Have a fun one for the Workers team...

Similar Threads

Have a fun one for the Workers team...

Similar Threads

Similar Threads

Similar Threads