Wappler Version : 4.4.2
Operating System : MacOS
Server Model: NodeJS
Database Type: MSSQL
Hosting Type: NodeJS
Expected behavior
No error is expected when accessing images from AWS s3 bucket.
Actual behavior
I’m storing images in AWS s3 bucket. I ran npm update command in the project folder and since then I have been getting aws-crt-nodejs.node error on all the pages where images from AWS s3 buckets are being downloaded to display. Node version 17.1.0
The images display correctly after I click Cancel on the pop-up message. I have also noticed that the file lib/modules/s3.js has changed after running the update command.
How to reproduce
Run npm update command for an existing project (v4.4.2) with AWS s3 bucket integration
Pages where images are downloaded from s3 show an error (screenshot attached)
This is just one native module part of the AWS sdk, that gets now installed locally, but isn’t signed by Apple. It happens only if you run node locally on Mac.
It is not a critical module and you don’t need it usually locally but if you want it you can just allow it’s installation in the Mac settings / security
The module is a peer dependency of the aws-sdk module. The module is not required, it is optional. If you run npm install or npm update from the command line then it will install this module (with npm 7 or higher, npm 6 will not install it). When you use Wappler, the optional modules will not install.
You’re right @patrick, I ran npm update from the command line instead of running the inbuilt Wappler command. I’ll remember to use Wappler command in the future. Thank you explaining the difference between running install / update from the command line or via Wappler.
