[WIP2] chore(deps-dev): yarn set version berry #3252
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's replaced by .yarnrc.yml in yarn modern https://yarnpkg.com/getting-started/qa#how-easy-should-you-expect-the-migration-from-classic-to-modern-to-be
|
The existing error is likely related to customizations in lerna ERR! yarn run build exited 1 in '@aws-sdk/client-sts'
lerna ERR! yarn run build stdout:
[build:cjs] yarn run build:cjs exited with code 0
[build:es] yarn run build:es exited with code 0
[build:types] src/runtimeConfig.browser.ts(21,14): error TS2742: The inferred type of 'getRuntimeConfig' cannot be named without a reference to '../../../packages/middleware-signing/node_modules/@aws-sdk/signature-v4/dist-types'. This is likely not portable. A type annotation is necessary.
[build:types] src/runtimeConfig.native.ts(9,14): error TS2742: The inferred type of 'getRuntimeConfig' cannot be named without a reference to '../../../packages/middleware-signing/node_modules/@aws-sdk/signature-v4/dist-types'. This is likely not portable. A type annotation is necessary.
[build:types] src/runtimeConfig.ts(32,14): error TS2742: The inferred type of 'getRuntimeConfig' cannot be named without a reference to '../../../packages/middleware-signing/node_modules/@aws-sdk/signature-v4/dist-types'. This is likely not portable. A type annotation is necessary.
[build:types] yarn run build:types exited with code 1
lerna ERR! yarn run build exited 1 in '@aws-sdk/client-sts'In this PR, we reintroduced star dependency for client-sts in karma-credential-loader as yarn install is successful with berry |
It's required to be installed globally Refs: https://yarnpkg.com/getting-started/install#install-corepack
|
Superceded by #3494 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Refs: #3182 (comment)
Reasons to bump to yarn modern https://yarnpkg.com/getting-started/qa#why-should-you-upgrade-to-yarn-modern
The experimental projects in aws-samples repo have been using yarn berry for some time now:
Description
Updates yarn version to berry.
Testing
ToDo: verify commands used in release scripts are successful.
Additional Context
Cleaned up PR of original attempt at #3235
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.