C
DThanks! Got any tips on how I should catch exceptions?
DGetting errors 1.5% of the time, not sure where.
AI am using D1 with Pages functions. Was working fine.
My D1 database had a binding in the function/worker of
My D1 database had a binding in the function/worker of
DB__D1_BETA__DB, anyone ever have seen this happen? Locally still works as expected (eg. DB
THello, any idea why Cloudflare function has such strong limitations on
For example, my team is using Astro (the framework) to generate a static site (SSG) and Astro is dumping routes such as:
The issue is that the Article slug is sometimes very long and we hit the 100 caracter limit (which is a very short limit for URI, but even wayyyy shorter for a complete path/url)
Also the
Is astro using in the wrong way Cloudflare feautres or are those strong limits known among developpers using cloudflare ?
_routes.jsonLimits
You may have no more than 100 include/exclude rules combined.
Each rule may have no more than 100 characters.
For example, my team is using Astro (the framework) to generate a static site (SSG) and Astro is dumping routes such as:
The issue is that the Article slug is sometimes very long and we hit the 100 caracter limit (which is a very short limit for URI, but even wayyyy shorter for a complete path/url)
Also the
100 include/exclude rules combined would mean that our blog cannot contains more than 100 articles ?Is astro using in the wrong way Cloudflare feautres or are those strong limits known among developpers using cloudflare ?
DThere has been a recent improvement in the routes generation in astro, here is the PR: https://github.com/withastro/astro/pull/7846
- you could try updating to that, or writing routes.json manually (not the best experience, I agree): you can remove everything from exclude, and only include routes or folders that need SSR, like
/api/*
GitHub
Changes
Fixes #6516
The cloudflare integration tends to create large _routes.json files, which quickly hits the limit of 100 combined include/exclude entries that Cloudflare imposes even for small ...
Fixes #6516
The cloudflare integration tends to create large _routes.json files, which quickly hits the limit of 100 combined include/exclude entries that Cloudflare imposes even for small ...
TThank you !
DNo problem! Let me know if the new version improves things magically, or if you had to do manual changes afterwards
TFor now team has reverted back to SSR and dropped SSG. But if it changes I’ll let u know
CQuestion about loading JSON:
We generate a small JSON file (1MB or so) during build time, and we'd like to load it at runtime for Functions.
Could we just
We generate a small JSON file (1MB or so) during build time, and we'd like to load it at runtime for Functions.
Could we just
import.bin extension?
HIIRC, JSON when imported is bundled as a JS object, so you shouldn’t need to make it binary instead
NHow does functions get built? I have a CRA project with craco and I'd like to do SSR to improve the first paint of my site, however when i import a component in functions i get errors about unknown loaders for svg, scss, etc. files so how should i configure my project to make this work?
NI tried figuring it out by looking at flareact's source but I'm a bit lost
HFlareact is really old, and afaik doesn’t support Functions. For Functions setups, you might want to go with a framework that actively supports Functions/Pages deployments, like Next or Astro
Nyeah i didn't want to go with flareact either since it doesn't support react 18 and it seems like it only has SSR and not hybrid mode (?); i just wanted to get an idea how to do SSR in workers
Ni tried astro once but it didn't worked out
Nit suggested basically a seamless change, but after hours of refactoring i still wasn't able to get my page to work
HMaybe try Next then? I know there has been some collab between the CRA team and Vercel, so it should be a bit easier to get working
Nafter your first message i already started looking through the docs 
CDoesn't seem like it's possible to
Have this file at
importHave this file at
functions/src/api.ts with the JSON under functions/builder/output.jsonCAlso have
resolveJsonModule set for TypeScript
Unot yet
Nbut if the file gets generated during build then it doesn't exists when evaluating dependencies, does it?
Nso i guess you need some multi stage build where first the file is generated then it's used
CIt gets generated in the build command of the Pages, so it's present before it worker is compiled
DI am having this issue as well on a new project. Name variable name (
DB__D1_BETA__DB. However in most cases I can't utilize either binding. Can anyone advise a path forward?
ASo weird. Are you seeing this behavior only in the deployed app as well?
DYeah. It is a Pages app, and I just found that the D1 binding works if I deploy via
wrangler pages deployFunctions don’t work at all if you use dashboard direct uploads
DHow were they working for me?
H
unless they added that recently, they shouldn’t be workingHWere you doing it via Git?
DNo
HDirect Uploads don’t run through a build, so something else must be happening…
DThe app is already built before I upload
HMaybe that’s why D1 didn’t work, since it has to be run through Wrangler to work
HThough there may be an update that removes the need for a shim
HWe do still recommend using Wrangler when using Functions though
DI'm only talking about the deployed app here, not local development
HD1 or not
HNo, I mean using wrangler pages deploy
DOk well when I upload via the web UI — which doesn't mention this limitation — I would get a KV binding and a binding to
__D1_BETA__DB which would sometimes be a D1 binding and sometimes an empty objectHIIRC, D1 Bindings, under the hood, are just a fetcher instance. When building with Wrangler, it will insert a shim that takes all the calls to env.D1, formats it a certain way, then passes it in to the Beta DB binding you found
HSo since you didn’t run wrangler to deploy it, it never inserts the shim, and thus D1 queries don’t work
AThat's interesting, thanks. Will dig a bit deeper when i get the time into if I can reproduce both broken/correct state with something on my side
KYou can't
JSON.stringify