koa-body | koa body parser middleware | REST library

I have a simple koa REST service wrote in typescript that has a GET request the simply returns all users from a firebase database at db ref /user.

The request gets received by the app and it gets the database reference, but it hangs forever when it should get the value.

This is my index.ts file:

When App run on local, I can upload file to Azure Blob Storage.

But when I deploy app to Azure App Service, it always responses 502 Bad Gateway

I use library koa-body to handle upload file

I have managed to make middleware work in Strapi. But, I can't see the body in the request.

Inside /middlewares/getEmail/index.js, I Have

I have router created with koa-router:

auth.js

I am attempting to upload a JSON object at about 1.5 mb from our React client to our Koa.js node.js server.

I am using Koa.js with koaBody (koa-body 4.1.1).

On HTTPS, in our production environment, I cannot upload the object, I receive a status of 413 from our server. However, in dev or on http, I have no problem uploading the file. I can change the jsonLimit to '1mb' and replicate the same error in dev, so I know the formatting is correct.

I have setup the configuration to handle up to '10mb'. Here is the code.

My app.js is as follows...

I followed this tutorial: https://shopify.dev/tutorials/build-a-shopify-app-with-node-and-react

From the beginning, my app was extremely slow to load, including when changing tabs, including when loaded through ngrok and run on localhost or deployed on app engine.

What could be causing this ?

P.S.: I am new to React, Next.js and Shopify App development, so the answer could be quite basic.

P.P.S.: The build output seems to indicate "First Load JS shared by all" is too large based on the red color. I do not know how to investigate this and reduce the size of said chunks although a mere 214KB could not explain such slow load times, could it ?

Build

React Dev Tools Profiler

@next/bundle-analyzer Output:

Parsed

Gzipped

package.json

I know there are a lot of articles out there regarding the cors preflight error:

http://70.xx.xx.60/oms/api/login' from origin 'http://order.example.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow- Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

However, I had this issue once when I was developing in my local environment, fixed it, and when I moved my server to a host (A2Hosting), despite enabling cors in the .htaccess file like they recommend, I have returned to getting this error. The following are the relevant files if anyone could take a look and offer insight as to why this issue has popped up again after being resolved once. I am not looking to download the chrome plugin workaround, and I would like to avoid a proxy, I'd prefer to just setup cors correctly and forget about it.

my server.js:

I have an app where I need to send data from React frontend to Koa server. Problem is that I have no idea how to print out request body in Koa.

In React I run this code on click