es6-promisify | Convert callback-based javascript to ES6 Promises | Reactive Programming library

I have an express server that uses a local json file for a database. I'm using https://github.com/typicode/lowdb for getters and setters.

Currently the server keeps starting and restarting without any problems, but can't access it. Below is my Server.js file:

I am working on lex and I am trying to store user data in DynamoDB while using NodeJS

Here is my code:

How to get the certificate ID / fingerprint of an x.509 certificate using node-forge?

Update

I need this for AWS IoT. I've been investigating and ended up that AWS probably uses some fingerprint algorithm to extract the certificate ID. It is not baked into the cert, probably the public key is used as a base for the fingerprint.

Update 2

Running this command returns the correct fingerprint: openssl x509 -noout -fingerprint -sha256 -inform pem -in cert.crt

How to achieve this with node-forge?

I've put together the following one but it does not return the same fp.:

The following code shows me the error:

TypeError: Right-hand side of 'instanceof' is not callable

There seems to be a problem here with the es6-promisify library

When in Postman I use the 'POST' method and url: http: // localhost: 7777 / register, I also chooseBody and row and paste the object{name: 'Martin}. Why in [" You must supply a name! "," That Email is not valid! "," Password Cannot be Blank! "," Confirmed Password cannot be blank "," Oops! Your passwords do not match "] returns me You must supply a name!"Since I gave my name in body? In addition, it gets the status: 500Internal Server Error.

Routes: index.js

For the source code containing:

I'm using upload method from aws-sdk to upload files to S3 bucket from React app in browser.

The original callback based upload method is as bellow:

After running npm audit fix fto fix a vulnerability, pupetteer is no longer able to navigate to anything, not even google.

npm list says I am using 1.16.0.

In a script named invoice_to_pdf.js:

I see this on two different machines. When I navigate to the folder that contains my package.json file and execute the command yarn list, it lists a bunch of packages that I haven't installed. If I execute the command yarn check then it complains that most of the packages aren't installed.

So, what changed since the last time this worked correctly? Where is yarn finding all of the extraneous packages, and how do I convince it that they really aren't there?

Here are all of the relevant files in my project directory:

package.json