Cloudflare Developers•9mo ago

Ah I was thinking of keeping a Hono router around. To save CPU time for setup.

Sst3fan Ah I was thinking of keeping a Hono router around. To save CPU time for setup.

Isaac McFadyen•4/19/25, 7:49 PM

The way hono is designed, you keep the router in the global scope anyway - it's only initialized once at startup.

Isaac McFadyen•4/19/25, 7:50 PM

i.e. https://hono.dev/docs/getting-started/cloudflare-workers

const app = new Hono()

export default app;

const app = new Hono()

export default app;

st3fanOP•4/19/25, 7:50 PM

Yes but if I understand correctly it would be initialized for every http request handled?

Sst3fan Yes but if I understand correctly it would be initialized for every http request...

Isaac McFadyen•4/19/25, 7:50 PM

Nope, because anything outside of the fetchfetch handler (which Hono handles for you, in that example) is "global"

st3fanOP•4/19/25, 7:51 PM

That contradicts what @Ashley said earlier?

st3fanOP•4/19/25, 7:54 PM

I can add some logging to find out

Ashley•4/19/25, 7:58 PM

I’ve not used Hono tons, but I figured you wanted to cache something that was mutable which definitely won’t work typically.

Ashley•4/19/25, 7:58 PM

A given isolate has its own scope, but isolates are not necessarily long-lived. An isolate may be spun down and evicted for a number of reasons
Because of this, it is generally advised that you not store mutable state in your global scope unless you have accounted for this contingen

Ashley•4/19/25, 7:58 PM

From https://developers.cloudflare.com/workers/reference/how-workers-works/

Cloudflare Docs

How Workers works · Cloudflare Workers docs

The difference between the Workers runtime versus traditional browsers and Node.js.

st3fanOP•4/19/25, 8:08 PM

Hono, a GitHub api client, a webhook router. I think j it is all stateless. Thanks that is a good document!

st3fanOP•4/19/25, 8:10 PM

Yeah sounds like no guarantees but may shave some milliseconds off requests if I keep things around.

Walshy•4/19/25, 9:28 PM

Yeah if you re-use the isolate, what you put in global scope still exists. It can be a way to re-use across requests but there's no guarantee any 2 requests will hit the same isolate.

vg•4/20/25, 8:48 AM

For deploying a static Angular site, is it recommended to use Workers Static or Pages?

Walshy•4/20/25, 11:04 AM

?pages

SuperHelpflare•4/20/25, 11:04 AM

As announced during Developer Week, Cloudflare recommends all new projects use Workers Assets. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. If there is something missing that you think Workers needs, please send it in #workers-and-pages-feature-suggestions

st3fanOP•4/20/25, 3:30 PM

I have a thing running!

st3fanOP•4/20/25, 3:32 PM

But I have two "Uncaught exception" errors. I found those back in the logs and they are both "The script will never generate a response." errors with a http status 500. But there are no stack traces anywhere. What should I do to see those? (Assuming the platform catches them - I don't have any exception handlers because I wanted to see it from the platform side first)

st3fanOP•4/20/25, 3:42 PM

wrangler tailwrangler tail also tells me Exception ThrownException Thrown but no details other than Error: The script will never generate a response.Error: The script will never generate a response.

st3fanOP•4/20/25, 3:42 PM

Or is that the exception

st3fanOP•4/20/25, 7:36 PM

I was complaining about the secrets manager not accepting a PKCS#8 private key earlier but today I found out that there is also wrangler secretwrangler secret to manage a different set of secrets ... which takes longer secret values just fine. Competing technologies?

Sst3fan But I have two "Uncaught exception" errors. I found those back in the logs and t...

Chaika•4/20/25, 7:43 PM

generally it's because you're leaking promises/async stuff across requests in the global scope

"The script will never generate a response" happens when the runtime sees that it has finished executing all the JavaScript microtasks for a particular request, and no I/O operations have been scheduled

can be caused by a library you are using as well, there's a few that could cause it that are known issues, as well as just any that assumes globals are fine/persisting promises, which is ok in most other environments

Sst3fan I was complaining about the secrets manager not accepting a PKCS#8 private key e...

Chaika•4/20/25, 7:44 PM

wrangler secrets are much older, they're per worker and part of it, Secret store is account wide

keerth•4/20/25, 7:53 PM

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

I keep seeing this error when deploying, it's happening for a vite react app that I've deployed, and I've edited the code and redeployed

keerth•4/20/25, 7:53 PM

not sure if anyone seen it before, but can't figure out why it's happening

keerth•4/20/25, 7:53 PM

also I'm using the same git as the template, just even changing some code and redeploying makes this error occur

keerth•4/20/25, 7:54 PM

https://damp-violet-825c.keerthanenr.workers.dev/

keerth•4/20/25, 7:54 PM

example app here

keerth•4/20/25, 7:57 PM

https://github.com/keerthanenr/damp-violet-825c

GitHub

GitHub - keerthanenr/damp-violet-825c

Contribute to keerthanenr/damp-violet-825c development by creating an account on GitHub.

keerth•4/20/25, 7:57 PM

here's the repo for it

keerth•4/20/25, 7:57 PM

if anyone can see anything that could be causing this would appreciate it!

CChaika generally it's because you're leaking promises/async stuff across requests in th...

st3fanOP•4/20/25, 8:00 PM

I think my code is fine. I'm starting to think it is octokit that doesn't work well on Workers.

Kkeerth if anyone can see anything that could be causing this would appreciate it!

Chaika•4/20/25, 8:00 PM

bump your compat date back to 2025-03-31

Chaika•4/20/25, 8:01 PM

could be the new spa behavior is messing with stuff, easy thing to test
edit: looking at your code, you're trying to handle the *.js files, you'd need to enable your worker running of the assets ahead for that to work, if they're exact matches, your user worker won't be ran

Chaika•4/20/25, 8:01 PM

does it work in wrangler dev?

st3fanOP•4/20/25, 8:02 PM

worker secrets don't work for me unfortunately .. i set them with wrangler secret putwrangler secret put but they are empty in my app. I have an export interface Env { FOO_SECRET: string; }export interface Env { FOO_SECRET: string; } in my app but the string is empty.

st3fanOP•4/20/25, 8:05 PM

(i'm a noob and i accept some starting up pain but some of this stuf is ... uugghhh why are simple things so hard)

Sst3fan worker secrets don't work for me unfortunately .. i set them with `wrangler secr...

Chaika•4/20/25, 8:06 PM

if you're using local dev (the default of wrangler devwrangler dev), those secrets won't be pulled down, need to define them for local dev in .dev.vars file at the root of your project: https://developers.cloudflare.com/workers/configuration/secrets/#local-development-with-secrets

Cloudflare Docs

Secrets · Cloudflare Workers docs

Store sensitive information, like API keys and auth tokens, in your Worker.

CChaika does it work in wrangler dev?

keerth•4/20/25, 8:07 PM

yeah so after I tried to load the template in wrangler dev, it didn't work so I made those changes to try and make it work, will revert it back to the original code and make a small change to main.tsx

CChaika if you're using local dev (the default of `wrangler dev`), those secrets won't b...

st3fanOP•4/20/25, 8:09 PM

i am testing in production .. i think what may have gone wrong is that i assumed i had to add them to wrangler.jsonc as empty environment variables so that they are generated in the bindings/env .. but i think that may delete the secrets or override them .. from the docs is is unclear what the source of truth is

Sst3fan i am testing in production .. i think what may have gone wrong is that i assumed...

Chaika•4/20/25, 8:11 PM

yea that most likely cleared them. For everything but secrets the wrangler config local is the source of truth. It won't remove secrets if they're not present in there
https://developers.cloudflare.com/workers/wrangler/configuration/#source-of-truth

st3fanOP•4/20/25, 8:13 PM

so for secrets I need an interface Envinterface Env in my code that just lists those secrets .. but is that additive to the ones defines in wrangler.jsonc? I don't have any other bindings right now so i am not sure what happens next time in run wrangler typeswrangler types

st3fanOP•4/20/25, 8:14 PM

i'll find out because now that this works i am going to iterate and turn this little github app into a Durable Object

Sst3fan so for secrets I need an `interface Env` in my code that just lists those secret...

Chaika•4/20/25, 8:15 PM

looks like it picks up secrets defined in .dev.vars wrangler types command with secrets

Chaika•4/20/25, 8:15 PM

I'm no big typescript guy and have never moved on from manually creating the env type lol

st3fanOP•4/20/25, 8:16 PM

(Re the "The script will never generate a response" error - i need to experiment a bit - i have a weird feeling that the retry logic in GitHub's octokit library may be the culprit - it may be the only thing that does something with timers or globals. My own code is all straightforward async/wait .. i read it a couple of times and can't find any odd cases that may leak promises or not return a Response.)

keerth•4/20/25, 8:19 PM

Decided to use a new vite react template below

https://github.com/keerthanenr/yellow-snow-7ffe
https://yellow-snow-7ffe.keerthanenr.workers.dev/