yarnpkg/yarn

yarn add webpack produces javascript heap out of memory

Open

#6,511 opened on Oct 6, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
help wanted

Description

Do you want to request a feature or report a bug?

Bug What is the current behavior? yarn produces javascript heap out of memory issue when upgrading to webpack@4.20.2 particularly. I have not found it to be an issue when upgrading other packages.

further investigation shows that anything beyond 4.5.0 have this out of memory issue. I was able to successfully install webpack@4.5.0

If the current behavior is a bug, please provide the steps to reproduce.

git clone https://github.com/fobbyal/yarn-install-mem-heap-issue.git
yarn install
yarn add webpack@4.20.2

What is the expected behavior? yarn installs the webpack@4.20.2 succssfully.

Please mention your node.js, yarn and operating system version. yarn@1.10.1 node@8.10.0 on OSX and node@8.12.0 on arch linux

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsDebugging memory issues
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue is reproducible with webpack@4.20.2. Investigate the dependency resolution in yarn (possibly in 'src/package resolver.js' or similar) to understand why it runs out of memory. Also check if there are any linked issues or commits regarding memory usage in yarn 1.x. Since the repository is frozen, confirm that the bug exists in the current version or consider if it's fixed in the berry version.