Checkboxes for prior research
Describe the bug
This happens in a freshly created expo project. Installing the @aws-sdk/client-bedrock-agent-runtime npm package and then creating a client anywhere in the render tree causes the expo build to crash during bundling.
The resulting error is this:
Android Bundling failed 1377ms node_modules\expo-router\entry.js (1283 modules)
ERROR node_modules\@aws-sdk\client-bedrock-agent-runtime\dist-cjs\index.js: C:\[REDACTED]\test-app\node_modules\@aws-sdk\client-bedrock-agent-runtime\dist-cjs\index.js: Static class blocks are not enabled. Please add `@babel/plugin-transform-class-static-block` to your configuration.
455 |
456 | // src/BedrockAgentRuntimeClient.ts
> 457 | var BedrockAgentRuntimeClient = class extends import_smithy_client.Client {
| ^
458 | static {
459 | __name(this, "BedrockAgentRuntimeClient");
460 | }
Weirdly I can't find anything to do with @babel/plugin-transform-class-static-block online other than it being a run of the mill babel package. Either way, this prevents react native expo projects from using the sdk.
Additionally, I checked back as far as 3.787.0 and this still occurred
Regression Issue
SDK version number
@aws-sdk/client-bedrock-agent-runtime@3.823.0
Which JavaScript Runtime is this issue in?
React Native
Details of the browser/Node.js/ReactNative version
Expo sdk version 53.0.9 - a completely fresh build
Reproduction Steps
Create a new expo app using
npx create-expo-app@latest test-app
cd test-app
npm run android
(This will be a completely functioning template app)
npm install @aws-sdk/client-bedrock-agent-runtime
npm run android
(This will also work)
Now add these lines anywhere in the render tree, I did it in the top most _layout.tsx file
const client = new BedrockAgentRuntimeClient({});
console.log(`client is defined: ${!!client}`);
npm run android
(This will now fail and show the error I provided above)
Observed Behavior
A build error occurs during android bundling
Android Bundling failed 1377ms node_modules\expo-router\entry.js (1283 modules)
ERROR node_modules\@aws-sdk\client-bedrock-agent-runtime\dist-cjs\index.js: C:\[REDACTED]\test-app\node_modules\@aws-sdk\client-bedrock-agent-runtime\dist-cjs\index.js: Static class blocks are not enabled. Please add `@babel/plugin-transform-class-static-block` to your configuration.
455 |
456 | // src/BedrockAgentRuntimeClient.ts
> 457 | var BedrockAgentRuntimeClient = class extends import_smithy_client.Client {
| ^
458 | static {
459 | __name(this, "BedrockAgentRuntimeClient");
460 | }
Expected Behavior
The bundling should succeed, and then show an error at runtime because the client's configuration is empty
Possible Solution
No response
Additional Information/Context
I also tested expo sdk versions 52 and 51, both had the same result
Checkboxes for prior research
Describe the bug
This happens in a freshly created expo project. Installing the @aws-sdk/client-bedrock-agent-runtime npm package and then creating a client anywhere in the render tree causes the expo build to crash during bundling.
The resulting error is this:
Weirdly I can't find anything to do with @babel/plugin-transform-class-static-block online other than it being a run of the mill babel package. Either way, this prevents react native expo projects from using the sdk.
Additionally, I checked back as far as 3.787.0 and this still occurred
Regression Issue
SDK version number
@aws-sdk/client-bedrock-agent-runtime@3.823.0
Which JavaScript Runtime is this issue in?
React Native
Details of the browser/Node.js/ReactNative version
Expo sdk version 53.0.9 - a completely fresh build
Reproduction Steps
Create a new expo app using
npx create-expo-app@latest test-app
cd test-app
npm run android
(This will be a completely functioning template app)
npm install @aws-sdk/client-bedrock-agent-runtime
npm run android
(This will also work)
Now add these lines anywhere in the render tree, I did it in the top most _layout.tsx file
npm run android
(This will now fail and show the error I provided above)
Observed Behavior
A build error occurs during android bundling
Expected Behavior
The bundling should succeed, and then show an error at runtime because the client's configuration is empty
Possible Solution
No response
Additional Information/Context
I also tested expo sdk versions 52 and 51, both had the same result