fix: support new functions getter in edge functions

[43081j]

The serve function now accepts a functions getter rather than a plain object.

For example:

serve(async () => {
  return {
    someFunction: await doSomethingAsync()
  }
}, metadata);

Not sure how you want to handle landing this, since many clients will still be seeing the old server.ts which doesn't support this.

DRAFT since i imagine you folks are already on this internally, so feel free to throw this PR away if you're solving it elsewhere

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures
  we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
  something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures
  your code follows our style guide and passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

[eduardoboucas]

@43081j Can you clarify whether you're seeing an error because of this and where? Thanks!

[43081j]

@eduardoboucas

xh https://edge.netlify.com/bootstrap/server.ts

gets me this (truncated):

export const serve = (
  functions: () => Promise<Record<string, EdgeFunction>>,
) => {
  // ...
}

this code fetches that same URL (via boot.ts which re-exports server.ts):

build/packages/edge-bundler/node/formats/javascript.ts

Line 57 in 9a25819

const bootImport = `import { boot } from "${bootstrapURL}";`

this line calls the function we imported (serve):

build/packages/edge-bundler/node/formats/javascript.ts

Line 81 in 9a25819

const bootCall = `boot(functions, metadata);`

this line defines functions:

build/packages/edge-bundler/node/formats/javascript.ts

Line 58 in 9a25819

const declaration = `const functions = {}; const metadata = { functions: {} };`

which isn't () => Promise<Record<string, EdgeFunction>> but rather Record<string, EdgeFunction>.

that results in these CI failures:
https://github.com/netlify/build/actions/runs/16618084393/job/47015500063?pr=6586#step:10:454

locally, these tests pass on the same machine i used xh on above to fetch the URL. which im guessing is because node has a cached copy of serve.ts in some kind of import cache? not sure whats going on there.

but you can see the types are different now. so presumably the hosted server.ts changed shape underneath us

EDIT

or the reverse could be true. i'm seeing a cached copy that was reverted, and node is seeing the correct version?

but CI has the same problem i do

[eduardoboucas]

I just wanted to understand whether you were seeing this in a published version of any of the packages (i.e. affecting users) or just in the test suite. From what you describe it's the latter. We're on it! Thanks for reporting.

[43081j]

Just in the test runs 👍

I have a lot of PRs so notice these things 😅