It can catch some that fall through, but you can also add it to an `onError()` handler.
It can catch some that fall through, but you can also add it to an
onError()
Fgotcha. I'm pretty new to hono/CF ecosystem. So a very dumb question:
how did you do this? did you do anything in your
If you're running your application on Cloudflare Workers, set a binding value named SENTRY_DSN, which will be used as the DSN.
how did you do this? did you do anything in your
wrangler.toml
Iyou can put that in your
wrangler.toml.dev.varsI've put it in there and am able to access the url, but I'm unable to access the instance:
c.get('sentry')(and thank you so much for your help)
Fjk, I got it. thank you!
Ihttps://github.com/honojs/middleware/tree/main/packages/sentry This was what I followed
GitHub
monorepo for Hono third-party middleware/helpers/wrappers - honojs/middleware
Fgot it. yeah, I got the errors firing into sentry. how did you handle source maps by chance?
II didn't. Source maps don't make sense for HTTP errors; either your route returned a success or an error. Any internal errors are probably going to be custom try/catch so you can put a more descriptive explanation of what went wrong.
JDoes anyone know why Access-Control-Allow-Credentials causes an Invalid Header error in Cloudflare Page Functions? 
IHow have you defined the header?
JJust like new Response(null, { status:200, headers: {"Access-Control-Allow-Credentials": "true" })
JWith the standard other CORS headers
JHi, when I use fetch to do sub request, when headers contains
headers.set('Accept', 'application/json');When remove this header, fetch successfully...
EWhat's the reproduction code? Any other code or libraries included?
KHi, any plans to bring the rate limit feature from workers to pages functions?
ZHello everyone, everything ok?
I'm working on a project with nextjs 14 and when I upload the project to cloudflare pages. Only one page works in SSR. The others do not load the fetch. Has anyone had this problem and know how to solve it?
I'm working on a project with nextjs 14 and when I upload the project to cloudflare pages. Only one page works in SSR. The others do not load the fetch. Has anyone had this problem and know how to solve it?
Jany updates on Node working the same as on Workers? Still having issues with Knex
HWhat was the specific issue? Functions/Workers are explicitly not node, even with
nodejs_compat
Jcompatibility_flags = ["nodejs_compat"]node_compat = true@HardlyWorkin' something that works on Workers is not working on Pages Functions
HYeah, so what explicitly is the issue? I can only help if I know exactly what is going wrong
J@HardlyWorkin' a package that works on Workers doesn't work on Pages Functions. It throws errors when trying to build about the imports
J@HardlyWorkin' this works fine on workers: https://github.com/sutandojs/sutando-examples/tree/main/typescript/rest-hono-cf-d1
But if you were to use the package within a Nuxt project - it won't build.
But if you were to use the package within a Nuxt project - it won't build.
GitHub
Examples using Sutando. Contribute to sutandojs/sutando-examples development by creating an account on GitHub.
NHi there, I am using a NextJS based pages project using the GIT integration. I have a very simple worker (in functions folder, a hello world).For some reason on latest builds I do not see this worker being deployed anymore.
J@HardlyWorkin' are you able to look at deploy logs?
HSorry, was a bit busy, let me catch up with this thread...
HOk, I see what might be the issue. It appears the project uses the
node_compat
Jit's not building with the wrangler file for Pages/Functions
HI'm not sure I understand what you are saying?
JI pinged you in the thread
Tanyone have advice on debugging a 500 for my ssr app? finally got my first build to go through but I just get a 500 page, and since its ssr, all i get from going to the page is the 500 error page without any way to see what the actual error is. Also don't see anything on the functions metrics page
Tnvm found the Real-time Logs section in the functions tab of my deployment
PI’m seeing a p99 of 95ms and a p50 of 4.6ms on CPU time for functions after deploying the next js starter app to pages. What’s going on here? Why are these values so high?
Hلطفاً طبق قوانین #
welcome-and-rules سؤال خود را در چندین کانال پست نکنید. برای افرادی که سعی در کمک به شما دارند سردرگمی ایجاد می کند و مشکل یا سوال شما را سریعتر حل نمی کند.
welcome-and-rules سؤال خود را در چندین کانال پست نکنید. برای افرادی که سعی در کمک به شما دارند سردرگمی ایجاد می کند و مشکل یا سوال شما را سریعتر حل نمی کند.
HIt updates a local version of your KV namespace in
.wrangler
BI'm deploying a Nuxt app however it seems like an import from one of my dependencies is undefined. I'm importing
samlifynode-forgeTypeError: Cannot read properties of undefined (reading 'decode64') at ....Plus I'm not sure if this is a Functions question or a Workers question. I think it deploys functions but I'm new to this.
D
FPlease do not post your question in multiple channels per the rules at #welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
SHello, I have set a Service bindings in my worker pages setting to be able to request from the statically web page(built with vite) I deployed in pages to a worker. My issue is that I don't know how to access the env variable from my static page code to get the env.SERVICE.fetch call(I tried using import.meta.env but that doesn't work). HELP.
HYou can't access bindings during build, if that is what you mean
SBut how I'm supposed to access them from a static web page(I don't want to access them in development/local, I eman production once it is deployed), will the env variable be accessible? In a worker the context comes from the event onRequest but how from a worker page?
HFrom a completely static page? You can't
HBindings are available at runtime