Edge function configuration: build validation fails if path is array

Support
,
1

According to the docs at Edge Functions declarations | Netlify Docs path can be an array of strings. When trying this out (say `[ “/one/", "/two/” ]), the deploy fails with the following message:

...
8:20:21 PM: Edge Functions bundling                                       
8:20:21 PM: ────────────────────────────────────────────────────────────────
8:20:21 PM: ​
8:20:21 PM: Packaging Edge Functions from .netlify/edge-functions directory:
8:20:21 PM:  - server
8:20:25 PM: ​
8:20:25 PM: Bundling of edge function failed                              
8:20:25 PM: ────────────────────────────────────────────────────────────────
8:20:25 PM: ​
8:20:25 PM:   Error message
8:20:25 PM:   Validation of Edge Functions manifest failed
8:20:25 PM:   TYPE must be string
...

Is the documention correct or there is a bug in the bundler? The declaration in the code seems to indicate that no array is expected (build/packages/edge-bundler/node/declaration.ts at d2276a9e29630a2c14b271cadedbb6d44151225e · netlify/build · GitHub)

2

Seems to work fine: hrishikesh-k/f-143644, f-143644.netlify.app/test

3

Oh, then there is a mismatch in what can be done inline in the edge function config (your example) and what can be done through an integration (as documented in Create an Edge Functions integration | Netlify Docs). The error I was showing happens when bundling the edge function, configured through manifest.json. Error is triggered by having the following config:

...
  path: ["/one/*", "/two/*"],
...
4

Happy to review a minimal reproduction. You also might be interested in Frameworks API: Frameworks API | Netlify Docs