Sean Massa 5dc6f48e44 [cli][dev] handle no response from edge functions (#8095) ...

When an edge function has no response during `vc dev`, we were seeing an unhelpful error message:

> The event listener did not respond.

Now, we'll see a much more specific error message:

> Unhandled rejection: Edge Function "api/edge-no-response.ts" did not return a response.
> Error! Failed to complete request to /api/edge-no-response: Error: socket hang up

2022-07-20 20:09:29 +00:00

..

edge-error-config.js

[cli][node] make error handling of edge functions consistent with serverless functions in vc dev (#8007)

2022-06-28 04:12:21 +00:00

edge-error-no-handler.js

[cli][node] make error handling of edge functions consistent with serverless functions in vc dev (#8007)

2022-06-28 04:12:21 +00:00

edge-error-runtime.js

[cli][node] make error handling of edge functions consistent with serverless functions in vc dev (#8007)

2022-06-28 04:12:21 +00:00

edge-error-startup.js

[cli][node] make error handling of edge functions consistent with serverless functions in vc dev (#8007)

2022-06-28 04:12:21 +00:00

edge-error-syntax.js

[cli][node] switch to esbuild for compiling edge functions (#8032)

2022-06-28 11:27:56 -05:00

edge-error-unknown-import.js

[cli][node] make error handling of edge functions consistent with serverless functions in vc dev (#8007)

2022-06-28 04:12:21 +00:00

edge-no-response.js

[cli][dev] handle no response from edge functions (#8095)

2022-07-20 20:09:29 +00:00