nodejs.org | The Node.js® Website | Runtime Evironment library

Not really an answer but I want to share what ended up working: I did the debugging with Webstorm. Worked on the first try after following the Jest / Webstorm debugging guide. I set a breakpoint in the test, started the debugging in Webstorm and voila it hit the breakpoint.

Add this in your Jest Configuration (e.g. jest.config.json)

In S3 you can use the Upload class from @aws-sdk/lib-storage to do multipart uploads. Seems like there might be no mention of this in the docs site for @aws-sdk/client-s3 unfortunately.

It's mentioned in the upgrade guide here: https://github.com/aws/aws-sdk-js-v3/blob/main/UPGRADING.md#s3-multipart-upload

Here's the example provided in https://github.com/aws/aws-sdk-js-v3/tree/main/lib/lib-storage:

glob error [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {

This means it is trying to read something on 'root' directory, something which always needs root access.

Try to run the command like this:

You are trying to upload an image from a local relative path which is wrong at the moment.

But I'm not sure if the API handles local images with the proper path and even if you use absolute path.

The best approach will be to read the image with Node.js and convert it to Base64 and pass it that way. You can refer to the docs here: https://shopify.dev/api/admin-rest/2021-07/resources/product-image#[post]/admin/api/2021-07/products/{product_id}/images.json

In addition please note that async/await doesn't work in a forEach function. So at the moment you are stacking all the uploads at the same time and the API will not be happy.

PS: Give my regards to Zoro/Marto & Evgeni. ;)

Both codes use the OpenSSL proprietary key derivation function EVP_BytesToKey() with an iteration count of 1 and MD5 as digest.
NodeJS does not use a salt, while CryptoJS applies a random salt. For this reason, the NodeJS result is unchanged for each encryption, while the CryptoJS result always changes (assuming the same plaintext and passphrase).

Thus, to get the result of the NodeJS code with the CryptoJS code, you must not use a salt. However, by default, a salt is always applied. This can only be circumvented by explicitly determining key and IV with the key derivation function EvpKDF and then using both in the encryption:

Upgrade your node version, you're using the newest npm version, and it doesn't support old versions of node

Since you're on ubuntu i recommend you to use nvm

sudo apt-get install nvm

After searching for some time turns out i was using cypress 8.7.0 which was causing the issue, i downgraded to cypress 8.5.0 and it started working, hope that helps anyone else having this issue

Here's a hypothesis (that can be experimentally proven).

The difference in behavior between good and bad can be explained by the order of awaits.

In bad you're awaiting on throwError after you have awaited on doSomething, while in good, you're awaiting on Promise.all, which will not return until both are fullfilled or at least one is rejected (which will be the case here).

So in bad, the throwing is happening outside of await, and your catch is not triggered, and it is caught internally by node.

If you change your bad so that you await on throwError first, then your catch will get triggered: