but i removed this line, not sure why it was there and things seem to function without issue

but before it was working without issue, don't know if things got more strict. I had previously been set up as a service worker and then converted the whole project to module, so perhaps service worker was more forgiving

I'm probably overthinking this, is there a way I can trigger a function once my Worker is done streaming a response?

Someone has a quick tip how to combine Hono with a scheduler? Currently I just export default the hono instance

I don’t think so

This is what I use

typescript
export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext) {
        return app.fetch(request, env, ctx)
    },
    async scheduled(_: ScheduledEvent, env: Env, ctx: ExecutionContext) {
        ctx.waitUntil(someFunction(env, ctx))
    },
}

fetch: app.fetch,

should also work in the

export default

block

so it does. TIL

although that is a dangerous pattern in js, passing in

ctx.waitUntil

wouldn't work without

.bind(context)

I assume you mean when you don't use Kian's version?

It's not the case for hono in either case I believe, context however loses this if you pass it without `.bind`ing it to context, so it just doesn't

waitUntil

I thought that was only if you explicitly passed waitUntil as a method - instead of the entire context

Yeah, I just checked some code, passing around ctx is fine

yup, which is kinda the case if

fetch

 wasn't the fetch of the worker, but something that needs a fetch method from an app

ah yeah that's entirely fine, the equivalent of that would be exporting hono directly in some way rather an instance method, such as fetch or indeed waitUntil

I do not fully understand. Where do I need to add

.bind

?

you should be all good without bind in this case 👍

sorry if my comment caused confusion 😄

Ah k, no problem

does someone know if workers suppor this library

const crypto = require('crypto');

answered in a thread

Anyone that has used web crypto that can helpme translate this code snippet

js
getSign() {
        var sign = crypto.createSign('RSA-SHA256');
        sign.update(this.cadenaOriginal);
        sign.end();
        const key = fs.readFileSync('ssl/key.pem');
        let signature_b64 = sign.sign(key, 'base64');
        return signature_b64;
    }

or using CryptoJs

Can it be async

@Ceru © any quick feedback on this coding question? banging my head on trying to get a custom webpack build going https://discord.com/channels/595317990191398933/846453104382836766/1082413032732381204

how are you testing this? miniflare or using wrangler dev

wrangler dev

as far as i can recall

{ default: fetch }

isnt how its detected

it needs to be exported as a module

i believe i've tried all possible output styles from commonjs --> module. but let me do that one specifically