simple express api calling external end point through fetch failing with TypeError: o is not a function

Hi
I followed examples/basic-starter-api-gateway-v1 setup and updated app.js to include a new endpoint definition that uses fetch to call an external end point , external rest endpoint implemented within express returns a json response ( verified through postman ). However the fetch call is throwing this error ( zip of the root folder that includes my app.js is attached
[my-serverless-express.zip](https://github.com/vendia/serverless-express/files/6713379/my-serverless-express.zip)
)
*******************************************************************
2021-06-24T04:30:31.822Z aa7e4631-258c-4ed2-9ae0-b410af797e86 INFO TypeError: o is not a function
at fn (/var/task/webpack:/@vendia/serverless-express-example/src/app.js:102:28)
at r.handle_request (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/layer.js:95:5)
at next (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/route.js:137:13)
at p.fn [as dispatch] (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/route.js:112:3)
at r.handle_request (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/layer.js:95:5)
at done (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/index.js:281:22)
at Function.process_params (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/index.js:335:12)
at next (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/index.js:275:10)
at fn (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/middleware/init.js:40:5)
at r.handle_request (/var/task/webpack:/@vendia/serverless-express-example/node_modules/express/lib/router/layer.js:95:5)
********************************************************

Ispeziona examples/basic-starter-api-gateway-v1 e l’app.js allegato, in particolare l’endpoint alla riga 102 mostrato nello stack trace. Confrontalo con l’endpoint Express verificato tramite Postman e traccia il motivo per cui la chiamata esterna a fetch produce il TypeError. Il lavoro è completato quando la route basata su fetch viene eseguita correttamente e restituisce la risposta JSON prevista.

Scritto dal modello di indicizzazione a partire dal testo della issue.