LI saw CF Pages now also suports Static Assets for the most part
INo. Assets for Workers are still in beta.
IPages and Assets are two different things.
LI meant the "it may be supported in Cloudflare Pages" sentence in the card.
IAh. Assets is fairly feature-complete but Pages still has certain things that aren't in Static Assets (such as _routes.json or path-based routing)
LMaybe I remember things wrong.
LI'm pretty sure when the feature was launched last September, it was only available for Workers
LThe Cloudflare Blog
To celebrate Builder Day 2024, we’re shipping 18 updates inspired by direct feedback from developers building on Cloudflare. This includes new capabilities, like running evals with AI Gateway, beta products like Queues and Vectorize graduating to GA, massive speed improvements to KV and Workers AI, pricing simplifications, and bringing key featu...
II think you're confusing things. What that doc line means is that they are two different products, with Workers Assets being the newer (preferred) version, but Workers Assets is in beta and so some things in Pages may not be in Workers Assets yet.
LIs there any reason to prefer Pages once all features are supported by Workers?
INo, not really.
IAnd Pages will likely (eventually) be deprecated, but it's not at the moment.
LI thought so.
LProvides information about using runners with AWS CodeBuild.
CWorkers have no where near the power needed to be a runner
CAnd Cloudflare doesn't offer compute that other providers do
PWhere should i report a "bug"? The example code here is wrong 
LSo how does Cloudflare Builds work?
CI am not sure if that information is public
C
LAnd cannot that be used for running GitHub workers?
COnce it launches maybe, depends on how easily they give it to the public
Cmight not make sense cost wise and such
LI thought Cloudflare Builds had no coldstart at all, but I read that's 10s now?
L
LKinda in-line with GitHub Actions runners hosted on Azure to be fair.
CCloudflare workers don't (well.. mostly), maybe that's what you're thinking of?
Cthey advert Workers having no cold start in quite a few places but never builds as far as I know lol
Wyeah workers != builds
Wbuilds is it's own product but part of the workers suite
MDid you manage to fix it ?
MGreat tip, 100% agree with it
Jlol, i literally created a library yesterday for that reason
Jfor easy ssr in workers using html templates
Jnpm
A library for rendering dynamic HTML templates with embedded server-side JavaScript without using eval.. Latest version: 1.0.0, last published: 20 hours ago. Start using forge-templates in your project by running
npm i forge-templates. There are no other projects in the npm registry using forge-templates.Lso Builds is just normal VMs, not V8 isolate
Wyeah, it's just a build server - it's basically just GitHub Actions and Workers is the app GitHub Actions deploys
SDoes anyone know if
"not_found_handling": "single-page-application"
KDoes Pages/Workers support using
pnpm
Syes you can
Khow does one do that?
S^ and make sure to use pnpm in your build script. either in the dashboard in wrangler
Kah no, I meant when building the site at cloudflare
Syes
Kah ic
Kis there a way to force it to use --frozen-lockfile or is it auto-set to do that?
Sas you see i dont defined that arg and it still used it
Sregarding this i was missing a catchall with
env.ASSETS.fetch"not_found_handling": "single-page-application"
AWhen using the new automated worker builds, how is it possible to access configured build secrets? For example I would like to execute drizzle migrations on push to main, before deploying to workers. But I don‘t get the database url within drizzle config currently!
