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

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

J

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

Yes! Next is supported

P

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

Amazing

P

PlaidShamanOP•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 ...

J

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

Just pinned the message that has the form

P

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

S

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

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

B

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

how can i get started with build caching?

Bbigansh how can i get started with build caching?

C

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...

B

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

done

J

Jacob•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...

B

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

awesome. thank you

J

Jacob•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.

V

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

^ @945732495889014814

VVero ^ <@&945732495889014814>

L

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...

V

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

thanks, raising

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

C

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

Only lists nextjs, gatsby and Astro to start.

J

Jacob•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/

A

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

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

A

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

wrangler

wrangler

wrangler

wrangler

A

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...

H

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

A

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

H

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

H

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

It only applies when you don’t build it yourself

A

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

ahh, Pages Builds = build from Git?

H

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

Or your CI does

A

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

i see

AAvi ahh, Pages Builds = build from Git?

H

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

Yes

A

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

that’s a bummer

AAvi that’s a bummer

H

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

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

A

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

H

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

Probably the way to go

A

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

word. thanks!

A

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...

J

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...

J

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...

A

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

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

A

Andrew Ferk•10/2/23, 5:14 PM

Specifically, I think

.yarn/cache

.yarn/cache

.yarn/cache

.yarn/cache needs to be cached for the "Fetch step" and

.yarn/install-state.gz

.yarn/install-state.gz

.yarn/install-state.gz

.yarn/install-state.gz needs to be cached for the "Link step".

R

reitznerdomenik•10/3/23, 8:14 AM

Hi, is there any plan to extend the build caching to nuxt3 as well?
Or is there a way to hack around it and use those predefined folders for caching?

G

Georges•10/3/23, 9:02 AM

I was wondering if you would consider adding the

.jampack/cache

.jampack/cache

.jampack/cache

.jampack/cache used by jampack. A user has been asking for it https://github.com/divriots/jampack/issues/106

G

Georges•10/3/23, 9:04 AM

If

jampack

jampack

jampack

jampack is too small for you to consider it, could you add a generic folder like

".build_cache"

".build_cache"

".build_cache"

".build_cache" or something so projects don't need to highjack existing folders to work around it?

Aadaptive Was the beta suspended? I can't see it on the dashboard.

J

James•10/3/23, 4:46 PM

If you're using v2 build image (system), it should just be an option in the UI: https://i.james.pub/file/2023/10/6dbcb864-d5f0-4f77-b03a-ad7b1ffe1a3f.png

J

James•10/3/23, 4:47 PM

Actually I think the UI is always present, but it only works in v2 build image afaik

C

Cretezy•10/3/23, 8:48 PM

Is there a way to customize the cached paths?
We have Next.js under a sub-directory, so

.next/cache

.next/cache

.next/cache

.next/cache doesn't work. We don't want to update the root directory option (since we have

functions

functions

functions

functions and

web

web

web

web/Next.js as top-level directories in our repo)

J

James•10/4/23, 12:16 AM

Not at this time, as far as I now

C

Cretezy•10/4/23, 5:01 AM

Okay, thank you. That seems like an important feature

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

Similar Threads

Similar Threads

Similar Threads