yarnpkg/yarn

switch to node-tar@3 if it got faster than tar-fs

Open

#3380 opened on May 11, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-performancegood first issuehelp wantedtriaged

Description

https://github.com/npm/node-tar/pull/108.

Check how new node-tar performs with Yarn and consider switching back to it.

Contributor guide

Tech stack
javascriptnodejs
Domain
cliperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.jsyarn codebasetar fs and node tar
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review the linked PR (node tar#108) to understand the performance improvements. Set up a local environment to benchmark tar fs vs node tar@3 with typical Yarn workloads. Check the yarn repository's contribution guidelines and note that Yarn 1.x is frozen, so this change might be considered only if there is a significant benefit. Consult the recent comments on the issue for any updates.