Skip to content

Use packageManager field to specify that we're using yarn@1.22.17 #3259

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
trivikr opened this issue Jan 27, 2022 · 1 comment · Fixed by #3260
Closed

Use packageManager field to specify that we're using yarn@1.22.17 #3259

trivikr opened this issue Jan 27, 2022 · 1 comment · Fixed by #3260
Labels
feature-request New feature or enhancement. May require GitHub community feedback.

Comments

@trivikr
Copy link
Member

trivikr commented Jan 27, 2022

Is your feature request related to a problem? Please describe.

The developers working on AWS SDK for JavaScript (v3) have to manually install yarn one time as it's not available by default.

$ aws-sdk-js-v3> node -v
v16.13.1

$ aws-sdk-js-v3> yarn -v
zsh: command not found: yarn

$ aws-sdk-js-v3> yarn
zsh: command not found: yarn

Describe the solution you'd like

Define packageManager field in package.json which specifies that we're using yarn@1.22.17

If developer is using Node.js >=16.10, the corepack will automatically install yarn@1.22.17. For Node.js <16.10, the developer can manually install corepack by running npm install -g corepack.

The corepack is being backported to v14.19.0

@trivikr trivikr added the feature-request New feature or enhancement. May require GitHub community feedback. label Jan 27, 2022
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 11, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
feature-request New feature or enhancement. May require GitHub community feedback.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant