Trivikram Kamat

Closing this issue, as it's not reproducible as per testing in https://github.com/aws/aws-sdk-js-v3/issues/2416#issuecomment-1430156717, and original author is not working on the project. If this issue is reproducible for you, please create...

> I've got a repro repo here: [dwightwatson/vite](https://github.com/dwightwatson/vite) This issue is not with the direct import of AWS SDK for JavaScript (v3). I see that you'd created an issue with...

There is no error in vite 4.1.0 dev/build command with `@aws-sdk/[email protected]`. I followed [Getting Started Guide](https://vitejs.dev/guide/) from vite. ```console $ yarn create vite ... success Installed "[email protected]" with binaries: -...

The AWS SDK for JavaScript team revisited this issue while testing Lambda Layers, and verified that the symlink workaround from https://github.com/vibe/aws-esm-modules-layer-support works. We recommend that workaround, as it's simpler.

The issue in https://github.com/aws/aws-sdk-js-v3/issues/2478 was resolved after detailed discussions. The TODO here is to create a new specific bug report, if the issue continue exists. If it doesn't, close the...

We discussed using async-await instead of creating promise.

Verified that VSCode pauses on Promise.reject when "Uncaught Exceptions" is turned on. Screen recording https://github.com/aws/aws-sdk-js-v3/assets/16024985/54a4fff2-b6c9-4a8c-9d78-18abded150eb

Looks like the bug wasn't fixed in `mockReset` I've created a new issue at https://github.com/facebook/jest/issues/13916

I think the implementation can be as simple as ```diff - if (cache && isCacheFeatureAvailable()) { + const packageManagerFromManifest = getNameFromPackageManagerField(); + if ((cache !== "" || packageManagerFromManifest) && isCacheFeatureAvailable())...

Related: https://github.com/npm/package-json/issues/83