[Pkg-javascript-devel] yarnpkg 1.9.1 is ready for unstable

[Paolo Greppi]

yarnpkg is listed here:
https://wiki.debian.org/Javascript/Main/packages
so I am pinging the team before uploading 1.9.1 to unstable.

I manually tested the only run-time dep (gitlab) and it does not break it (yarnpkg install works).

I double checked the embedded modules- they're 15

The versions we embed are the same as upstream declares in the yarn.lock file except for: 

./dnscache/package.json:    "version": "1.0.2",
dnscache@^1.0.1:
  version "1.0.1"

./hash-for-dep/package.json:  "version": "1.5.1",
hash-for-dep@^1.2.3:
  version "1.2.3"

./normalize-url/package.json:   "version": "4.5.0",
normalize-url@^2.0.0:
  version "2.0.1"

./query-string/package.json:    "version": "6.8.3",
query-string@^5.0.1:
  version "5.1.1"

./resolve-package-path/package.json:  "version": "1.2.7",
this is a run-time dependency not declared in yarn.lock

./string-replace-loader/package.json:  "version": "2.2.0",
string-replace-loader@^2.1.1:
  version "2.1.1"

./tar-fs/package.json:  "version": "2.0.0",
tar-fs@^1.16.0:
  version "1.16.3"

./v8-compile-cache/package.json:  "version": "2.1.0",
v8-compile-cache@^2.0.0:
  version "2.0.0"

... we're always using same or later versions.

BTW we're cheating on dependencies version here:
https://salsa.debian.org/js-team/node-yarnpkg/commit/eaaf53a07a23a110affc20146e8622a70b8641b0
and here:
https://salsa.debian.org/js-team/node-yarnpkg/commit/13f6217bcc8bc6281c16e628044886a925897bc0

If there are no objections I'll upload next week.

Paolo