Top yarn issues

When using an offline cache, yarn upgrade adds the new package to the cache but does not remove the old one

triaged
rmacklin picture rmacklin·2 Dec 2016·11 Comments
👍4

What is the equivalent to npm's NPM_CONFIG_REGISTRY environment variable?

cat-compatibility cat-feature good first issue help wanted triaged
mlcohen picture mlcohen·30 Nov 2016·5 Comments
👍7 😄1

yarn add fails

cat-bug os-windows
maffelbaffel picture maffelbaffel·26 Nov 2016·11 Comments
👍1

devDependencies are not installed when both `NODE_ENV=production` and `NPM_CONFIG_PRODUCTION=false` are set

cat-compatibility
joeyespo picture joeyespo·22 Nov 2016·5 Comments
👍16

error An unexpected error occurred: "TODO".

cat-bug
jwerle picture jwerle·17 Nov 2016·11 Comments

Consider using `lodash`.

wtgtybhertgeghgtwtg picture wtgtybhertgeghgtwtg·30 Jan 2017·4 Comments

`upgrade-interactive` makes confusion with dependency versions

cat-bug
daltones picture daltones·16 Nov 2016·5 Comments
👍4

Regression between 0.16.1 and 0.17.0 when building package using node-gyp?

MoOx picture MoOx·15 Nov 2016·4 Comments

Some Yarn output not compatible with a Solarized Dark theme

cat-compatibility
tribou picture tribou·5 Nov 2016·4 Comments

[0.19.1] [regression] Yarn does not use registry configuration

victornoel picture victornoel·26 Jan 2017·3 Comments
 Previous issues
Next issues