🐛 BUG: about miniflare HOT 3 CLOSED

I don't think this is because of the colon in the url but the fact that you don't return anything in your event handler. If you modify your script to look like this

addEventListener('fetch', event => {
    console.log('hello world') 
    event.respondWith(new Response("Hello"));
})

I no longer get the 500 response.

Also generally its recommended to use module syntax over the service worker syntax you have above.

from miniflare.

@jspspike thanks for the quick reply

I misunderstood the cause.

if you put in wrangler.toml the routes below, you will see get the 500 error:

routes = [
  { "pattern" = "my.test.site.com/*", "zone_name" = "mysite.com" }
]

This produces the error:

TypeError: Fetch API cannot load: test:a
    at Object.fetch (entry.worker.js:1004:36)

For syntax, I need to stick to addEventListener for now because of webpack. It doens't preserve the default entrypoint with target: 'webworker'

from miniflare.

Hey! 👋 This should be fixed by #699, which will be included in the next release. Please note, Miniflare 3 now lives in the cloudflare/workers-sdk repo, and new releases will be published there.

from miniflare.