Build serverless function separately?

[fredblols]

I have a site with one serverless function. The serverless function mostly returns a summary of some data which is committed to the repo, which is frequently updated. However whenever I update this data, it triggers a full rebuild of the site which is unnecessary since only the serverless files have changed.

Is it possible to cache the rest of the build? Seems like a pointless use of resources which all im doing is adding a data file to the serverless function.

[perry]

hmm, good question. Before we start digging into specifics, did you read through this guide? There might be something helpful in here.

[Support Guide] Making the most of Netlify's CDN cache

Last reviewed by Netlify Support - August, 2023 Our CDN derives much of its efficiency from files whose checksums don’t change between deploys. For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to …

if not, let us know.