You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building open next, it results in this error:
...
Bundling cache assets...
Bundling server function...
✘ [ERROR] Could not resolve "@aws-sdk/client-sso-oidc"
node_modules/@aws-sdk/token-providers/dist-cjs/index.js:50:79:
50 │ const { SSOOIDCClient } = await Promise.resolve().then(() => __toESM(require("@aws-sdk/client-sso-oidc")));
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "@aws-sdk/client-sso-oidc" as external to exclude it from the bundle, which
will remove this error. You can also surround this "require" call with a try/catch block to handle
this failure at run-time instead of bundle-time.
/home/user/repos/project-front/node_modules/esbuild/lib/main.js:1649
let error = new Error(text);
^
Error: Build failed with 1 error:
node_modules/@aws-sdk/token-providers/dist-cjs/index.js:50:79: ERROR: Could not resolve "@aws-sdk/client-sso-oidc"
at failureErrorWithLog (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:1649:15)
at /home/user/repos/project-front/node_modules/esbuild/lib/main.js:1058:25
at runOnEndCallbacks (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:1484:45)
at buildResponseToResult (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:1056:7)
at /home/user/repos/project-front/node_modules/esbuild/lib/main.js:1085:16
at responseCallbacks.<computed> (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:703:9)
at handleIncomingPacket (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:762:9)
at Socket.readFromStdout (/home/user/repos/project-front/node_modules/esbuild/lib/main.js:679:7)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:559:12) {
errors: [Getter/Setter],
warnings: [Getter/Setter]
}
Node.js v20.12.2
error Command failed with exit code 1.
You'll have to install these dependencies manually for the moment ( @aws-sdk/client-sts, @aws-sdk/client-sso-oidc ).
I think we should create an issue in the sdk repo https://github.com/aws/aws-sdk-js-v3. This is a breaking change since it will break every single app or lib that bundle the sdk and that don't have auto-install-peers
When building open next, it results in this error:
My node version:
20.12.2
My package.json dependencies:
On executing
yarn install
on the project with cleannode_modules
and with cleared yarn cache, I get the following warnings:All the warnings mentioned above come from changes made on the commit:
credential-provider-ini
: aws/aws-sdk-js-v3@5ce5600#diff-28efbabf690ae87c39e8de256188f7b9fd15aa1532509b46e32e470fc9a2d863credential-provider-web-identity
: aws/aws-sdk-js-v3@5ce5600#diff-49c28d1cb42fdaaf4abd3d902f98939000a16805f8a3b9e0be564e3df395cde7credential-provider-sso
: aws/aws-sdk-js-v3@5ce5600#diff-4dbb7c9cedcbb7e6e1bd314417ea693bc764e83828d64814fcf3ec398777274aIn this commit all the packages are moving this packages to
peerDependency
If more information is needed, please ask for it.
I have taken a look for duplicated issues, but could not find any.
EDIT1: Add more info.
EDIT2: Add more info again.
The text was updated successfully, but these errors were encountered: