Skip to content

The yarn process gets killed on EC2 t2.micro #158

Open
@trivikr

Description

@trivikr

Describe the bug

The yarn process gets killed on EC2 t2.micro

Steps to reproduce

Create a new EC2 t2.micro instance on AL2023 and run the following commands to install git and node

$ sudo dnf install git -y

$ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash

$ source ~/.zshrc && nvm install 22 && corepack enable

Clone the repository, and run yarn

Observed behavior

The yarn process gets killed on EC2 t2.micro

$  yarn
! Corepack is about to download https://repo.yarnpkg.com/4.4.0/packages/yarnpkg-cli/bin/yarn.js
? Do you want to continue? [Y/n] Y

➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 253ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ react is listed by your project with version 19.0.0 (paf0ce), which doesn't satisfy what @reach/router and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 19.0.0 (p1ec3a), which doesn't satisfy what @reach/router and other dependencies request (^16.8.0).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
Killed00: ⠴ ========================================----------------------------------------

Expected behavior

The yarn process to be successful, like it happens on t2.xlarge

$ yarn
! Corepack is about to download https://repo.yarnpkg.com/4.4.0/packages/yarnpkg-cli/bin/yarn.js
? Do you want to continue? [Y/n] Y

➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ react is listed by your project with version 19.0.0 (paf0ce), which doesn't satisfy what @reach/router and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 19.0.0 (p1ec3a), which doesn't satisfy what @reach/router and other dependencies request (^16.8.0).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 421 packages were added to the project (+ 343.44 MiB).
➤ YN0000: └ Completed in 4s 810ms
➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.20.2 must be built because it never has been before or the last one failed
➤ YN0007: │ husky@npm:4.3.8 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 5s 293ms
➤ YN0000: · Done with warnings in 10s 329ms

Additional context

Existing issues discussing memory usage of yarn
https://github.com/search?q=repo%3Ayarnpkg%2Fberry+%22Killed%22&type=issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions