RollupError: "RpcProtocol" is not exported

[moltar]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

When building with tsup (esbuild), I am getting the following error on recent versions of the SDK:

RollupError: "RpcProtocol" is not exported by "../../node_modules/.pnpm/@AWS-SDK+core@3.840.0/node_modules/@smithy/core/protocols.d.ts", imported by "../../node_modules/.pnpm/@AWS-SDK+core@3.840.0/node_modules/@aws-sdk/core/dist-types/submodules/protocols/json/AwsJsonRpcProtocol.d.ts".

Usually this happens when the type is not exported properly.

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-quicksight@3.840.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v22.16.0

Reproduction Steps

1. Use SDK v3.840.0
2. Try to build with tsup, and use type bundling option

Observed Behavior

RollupError: "RpcProtocol" is not exported by "../../node_modules/.pnpm/@AWS-SDK+core@3.840.0/node_modules/@smithy/core/protocols.d.ts", imported by "../../node_modules/.pnpm/@AWS-SDK+core@3.840.0/node_modules/@aws-sdk/core/dist-types/submodules/protocols/json/AwsJsonRpcProtocol.d.ts".

Expected Behavior

For build to pass.

Possible Solution

No response

Additional Information/Context

No response

[kuhe]

I was able to bundle v3.840.0 of @aws-sdk/client-quicksight using tsup. Please provide more detailed reproduction steps in an example repository.

[moltar]

https://github.com/moltar/aws-sdk-qs-bundle

[kuhe]

According to egoist/tsup#920 and my testing of your repo, running with

  "dts": {
    "resolve": false
  },

works around the issue. This is a problem with the bundler and not the SDK.

[kuhe]

The example repo errors with out of memory rather than anything to do with "RpcProtocol".

[moltar]

According to egoist/tsup#920 and my testing of your repo, running with

  "dts": {
    "resolve": false
  },

works around the issue. This is a problem with the bundler and not the SDK.

But I need it to be true. Of course if you decide to turn off random features willy-nilly you can consider something fixed. But that's now how it works.

This is a problem with the bundler and not the SDK.

In this case, please explain how using exactly the same bundler version, but a different SDK version makes this error come about? In the PR that fails this build, the ONLY change is that the SDK got upgraded.

[kuhe]

I ran the test with NODE_OPTIONS=--max-old-space-size=8096 pnpm t to avoid the out-of-memory issue. That is something for the bundler to fix.

I got

RollupError: "RpcProtocol" is not exported by "node_modules/.pnpm/@aws-sdk+core@3.840.0/node_modules/@smithy/core/protocols.d.ts", imported by "node_modules/.pnpm/@aws-sdk+core@3.840.0/node_modules/@aws-sdk/core/dist-types/submodules/protocols/json/AwsJsonRpcProtocol.d.ts".

This is from the bundler not understanding package.json exports. Although @smithy/core/protocols.d.ts exists in the package, it is not part of the imports.

From @smithy/core's package.json:

    "./protocols": {
      "module": "./dist-es/submodules/protocols/index.js",
      "node": "./dist-cjs/submodules/protocols/index.js",
      "import": "./dist-es/submodules/protocols/index.js",
      "require": "./dist-cjs/submodules/protocols/index.js",
      "types": "./dist-types/submodules/protocols/index.d.ts"
    },

The import of @smithy/core/protodols should route to ./dist-types/submodules/protocols/index.d.ts. Other bundlers understand this, and it is a standard part of Node.js & package.json files.

Secondly, RpcProtocol is in fact exported by the file from the error message, so the message doesn't make sense to me.

---

I'm not able to provide a deep investigation of tsup and why it is failing at this time. I suggest you can explore some of the solutions outlined in the issues within the tsup repository, or consider using another bundler that doesn't run into these issues.

[kuhe]

One potential solution may be to exclude the node_modules/@smithy/core/protocols.d.ts from the bundling process explicitly.

[moltar]

The import of @smithy/core/protodols should route to ./dist-types/submodules/protocols/index.d.ts. Other bundlers understand this, and it is a standard part of Node.js & package.json files.

Perhaps it should, but there's no such file:

https://www.npmjs.com/package/@smithy/core/v/3.6.0?activeTab=code