We found the issue to be in the mysql2 package version 3.9.4.
The following update is causing the error.
The probrem it is causing is that we depend on the .hasOwnProperty() method which no longer works after the update. An issue is already posted at their repo.
There is also a new pull request to revert this change and hopefully get applied soon.
We will investigate to improve the deployment process and lock the versions to prevent this kind of problems in the future.
For a workarround you can the mysql2 version to 3.9.3 in your package.json without the ^.