What if you have a different branch with vastly different settings? Maybe we could use the branch as

What if you have a different branch with vastly different settings? Maybe we could use the branch as a cache key instead? What if you change frameworks? (I guess we could rely on you hitting the Clear Cache button for that?)

JacobOP•9/20/23, 1:56 PM

We were trying to avoid users having to hit Clear Cache and having things just work.

JacobOP•9/20/23, 1:56 PM

But we weren't thinking about users updating deps every week

JJacob What if you have a different branch with vastly different settings? Maybe we cou...

itsmatteomanf•9/20/23, 3:17 PM

Oh, yeah. Branches for sure, I wasn’t gonna even mention that.

itsmatteomanf•9/20/23, 3:18 PM

Most frameworks tend to have their own cache folder, so it wouldn’t be a big issue…

Iitsmatteomanf Most frameworks tend to have their own cache folder, so it wouldn’t be a big iss...

JacobOP•9/20/23, 3:24 PM

I wonder what would be a good way to surface that "hey you should probably clear your cache once in a while if you make big changes." Like I'd hate to be downloading/uploading 300MB of extra junk that's no longer used on every build

JJacob I wonder what would be a good way to surface that "hey you should probably clear...

itsmatteomanf•9/20/23, 3:25 PM

Maybe some sort of diff in the package.json? If it changes too much give a nudge? I don’t know…

JacobOP•9/20/23, 3:27 PM

I want to add more config later - cache keys will probably be part of that. The current "play it super safe" approach will unfortunately come with some increased cache misses

JacobOP•9/20/23, 3:27 PM

The hope is that it will still save users some build time if they build a lot. We can improve more edge cases in the future

JJacob The hope is that it will still save users some build time if they build a lot. W...

itsmatteomanf•9/20/23, 7:25 PM

JacobOP•9/26/23, 8:40 PM

Heya! We released a few bug fixes & performance improvements. lmk if y'all see any issues!

JJacob Heya! We released a few bug fixes & performance improvements. lmk if y'all see a...

PlaidShaman•9/26/23, 10:19 PM

Hi Jacob! Does this work with next-on-pagesnext-on-pages?

PPlaidShaman Hi Jacob! Does this work with `next-on-pages`?

JacobOP•9/26/23, 10:25 PM

Yes! Next is supported

PlaidShaman•9/26/23, 10:26 PM

Amazing

PlaidShaman•9/26/23, 10:27 PM

I’d love to sign up for the beta. I looked at the stickied pins, but didn’t see anything to point me in the right direction.

Is there another place I could look?

PPlaidShaman I’d love to sign up for the beta. I looked at the stickied pins, but didn’t see ...

JacobOP•9/26/23, 10:28 PM

Just pinned the message that has the form

PlaidShaman•9/26/23, 10:28 PM

Samaritan•9/27/23, 2:44 AM

Super keen to be involved, have just filled in the form

bigansh•9/27/23, 7:40 AM

how can i get started with build caching?

Bbigansh how can i get started with build caching?

Cyb3r-Jak3•9/27/23, 11:44 AM

Can fill out the form on build-caching-beta

CCyb3r-Jak3 Can fill out the form on https://discord.com/channels/595317990191398933/1144554...

bigansh•9/27/23, 12:26 PM

done

JacobOP•9/27/23, 6:06 PM

Heya! Y'all should have access to it now

You can enable it in project settings -> Builds & deployments -> Build caching

JJacob Heya! Y'all should have access to it now 🙂 You can enable it in project setting...

bigansh•9/27/23, 8:29 PM

awesome. thank you

JacobOP•9/28/23, 1:24 PM

It's live! https://blog.cloudflare.com/race-ahead-with-build-caching/

The Cloudflare Blog

Race ahead with Cloudflare Pages build caching

Unleash the fast & furious in your builds with Cloudflare Pages' build caching. Build cache is a feature designed to reduce your build times by caching and reusing previously computed project components. Now in Beta for select frameworks and package managers.

Vero•9/28/23, 1:45 PM

^ @945732495889014814

VVero ^ <@&945732495889014814>

Luke•9/28/23, 1:47 PM

Join us on our Discord Server [link]

The blog post needs updating with the link

LLuke > Join us on our Discord Server [link] The blog post needs updating with the lin...

Vero•9/28/23, 1:47 PM

thanks, raising

GGlare Is Nuxt already included or is that in the "to come"?

Cyb3r-Jak3•9/28/23, 1:47 PM

Only lists nextjs, gatsby and Astro to start.

JacobOP•9/28/23, 3:12 PM

We also cache dependencies for Yarn 1, npm, pnpm, and bun!

JJacob It's live! https://blog.cloudflare.com/race-ahead-with-build-caching/

Avi•9/29/23, 4:50 AM

hi, i'm not seeing where it's possible to enable this...

Avi•9/29/23, 4:51 AM

worth noting that, because we need to integrate our pages deployments into our CI process, we deploy to pages manually via wranglerwrangler

Avi•9/29/23, 4:52 AM

i didn't see anything in the announcement about this being unavailable for that setup

AAvi worth noting that, because we need to integrate our pages deployments into our C...

Hello, I’m Allie!•9/29/23, 6:57 AM

Build caching only applies when using Pages Builds

HHello, I’m Allie!Build caching only applies when using Pages Builds

Avi•9/29/23, 6:58 AM

can you clarify exactly what that means? this is a pages project

AAvi can you clarify exactly what that means? this is a pages project

Hello, I’m Allie!•9/29/23, 6:58 AM

Yes, but you are using a Direct Upload, not the Pages Build-from-Git system

Hello, I’m Allie!•9/29/23, 6:59 AM

It only applies when you don’t build it yourself

Avi•9/29/23, 6:59 AM

ahh, Pages Builds = build from Git?

Hello, I’m Allie!•9/29/23, 6:59 AM

Or your CI does

Avi•9/29/23, 6:59 AM

i see

AAvi ahh, Pages Builds = build from Git?

Hello, I’m Allie!•9/29/23, 6:59 AM

Yes

Avi•9/29/23, 6:59 AM

that’s a bummer

AAvi that’s a bummer

Hello, I’m Allie!•9/29/23, 6:59 AM

It wouldn’t provide any benefit anyway, even if it was added tho

Avi•9/29/23, 6:59 AM

although i guess i could set up equivalent caching in my ci

AAvi although i guess i could set up equivalent caching in my ci

Hello, I’m Allie!•9/29/23, 6:59 AM

Probably the way to go

Avi•9/29/23, 6:59 AM

word. thanks!

Andrew Ferk•9/29/23, 6:55 PM

We just upgraded from yarn 1 to yarn 3

Does this mean we don't get the caching benefits of the package installer, given docs only say it supports yarn 1?

AAndrew Ferk We just upgraded from yarn 1 to yarn 3 😢 Does this mean we don't get the cachi...

JohnDotAwesome•10/1/23, 6:40 PM

We found that the guidance for caching yarn 3 was to commit the cache files to your repo https://yarnpkg.com/features/caching

yarn 3 caching has always been supported in a way

Cache strategies | Yarn

How to ensure your installs perform the absolute minimal amount of work.

AAndrew Ferk We just upgraded from yarn 1 to yarn 3 😢 Does this mean we don't get the cachi...

JohnDotAwesome•10/1/23, 6:41 PM

That being said, if you find something global and related to yarn3 that should be cached, please let us know

JJohnDotAwesome We found that the guidance for caching yarn 3 was to commit the cache files to y...

Andrew Ferk•10/2/23, 4:51 PM

This is something we were discussing last week. We currently are using the default yarn config, which is to do global caching. With the default yarn 3 setup, we are seeing the fetch and link step doing a lot of work. I don't think all of our stuff can be cached with yarn's capabilities, because some of our packages require machine/architecture dependencies to build. I assume then caching would need to be solved by the build machine.

You can see the fetch and link step below, when doing back-to-back builds of the same commit. These should essentially be noop with build caching.

11:28:27.392    ➤ YN0000: ┌ Fetch step
11:29:42.693    ➤ YN0013: │ 12 packages were already cached, 2585 had to be fetched
11:29:42.721    ➤ YN0000: └ Completed in 1m 16s
11:29:42.898    ➤ YN0000: ┌ Link step
11:31:08.063    ➤ YN0007: │ sharp@npm:0.30.7 must be built because it never has been before or the last one failed
... more ...
11:31:23.386    ➤ YN0000: └ Completed in 1m 41s

11:28:27.392    ➤ YN0000: ┌ Fetch step
11:29:42.693    ➤ YN0013: │ 12 packages were already cached, 2585 had to be fetched
11:29:42.721    ➤ YN0000: └ Completed in 1m 16s
11:29:42.898    ➤ YN0000: ┌ Link step
11:31:08.063    ➤ YN0007: │ sharp@npm:0.30.7 must be built because it never has been before or the last one failed
... more ...
11:31:23.386    ➤ YN0000: └ Completed in 1m 41s

What if you have a different branch with vastly different settings? Maybe we could use the branch as

Similar Threads