Call for testing yarnpkg 4 (Re: RFS: node-yarnpkg (update))
- To: debian-js@lists.debian.org
- Cc: debian-release@lists.debian.org
- Subject: Call for testing yarnpkg 4 (Re: RFS: node-yarnpkg (update))
- From: Pirate Praveen <praveen@onenetbeyond.org>
- Date: Sun, 29 Oct 2023 15:54:01 +0530
- Message-id: <[🔎] d3ab7a22-8d4b-439f-a015-5b1b0ad8cce0@onenetbeyond.org>
- In-reply-to: <CAFgEVL6o7cDVUREOjVx7u9rWAB-s+m90ZnMTXKPRbpTfN+o5Kg@mail.gmail.com>
- References: <CAFgEVL5+oNuB12Th708bYP_F2wZA=-NkagMX=c-4bSj6Uo_9NA@mail.gmail.com> <4c588a19-8c71-4193-b1b6-41e36dd66ffb@onenetbeyond.org> <CAFgEVL67QUwEHtSWUjH73BqOS5rtK=5EET+dp1Wa77Je7wnuYA@mail.gmail.com> <6b3c5850-e0db-42fb-8a44-bb497840c00d@onenetbeyond.org> <1eca0f1f-36c6-4d81-82f8-cc96bec15573@onenetbeyond.org> <CAFgEVL5sDNXhwS=wshW=xti2W1PSeBbbvWyJB642Rjm01O1Zwg@mail.gmail.com> <28793e5a-04cc-4ab2-ad13-5f4df87b8a37@onenetbeyond.org> <CAFgEVL4COga8w2bpe7xHsU7jV5K7SQxfM-zhMjbHmcqbcDnJYQ@mail.gmail.com> <2b82d16f-55a3-495c-9a65-81ed3ce20096@onenetbeyond.org> <CAFgEVL4M6z9e4u8E_KmFoX43ksRb6AAzESt1nxjF+u+RZY=RPg@mail.gmail.com> <d453f218-29d6-47ae-8c01-7a7b413dc15a@onenetbeyond.org> <CAFgEVL6o7cDVUREOjVx7u9rWAB-s+m90ZnMTXKPRbpTfN+o5Kg@mail.gmail.com>
On 13/10/23 8:26 PM, Israel Galadima wrote:
On Fri, 13 Oct 2023 at 13:57, Pirate Praveen <praveen@onenetbeyond.org
<mailto:praveen@onenetbeyond.org>> wrote:
I think I use coma separated list, but probably the other option
work too.
Thanks, I've fixed everything.
Thanks to great work by Israel and other outreachy interns in the past,
we have a yarnpkg in the archive that is built with well maintained
build and runtime dependendencies (we can finally get rid of obsolete
node-request from the archive). We can also stop maintaining patches to
make it build with newer build depends like babel 7.
We also have corepack, which is kind of a meta package manager - package
manager to install package managers!! (no surprise to people who know
nodejs). corepack can install npm, yarn or pnpm.
Currently yarnpkg 4 is in experimental, I would like these things
completed before we upload it to unstable.
1. Test the yarnpkg from experimental a bit, for example try to use it
in gitlab
2. Document how to use corepack yarn or node_modules plugin to get yarn 1.x
3. Create a NEWS file in yarnpkg to mention how to get yarn 1 behavior,
either by using corepack or by enabling node_modules plugin.
So please test yarnpkg from experimental and report any problems you notice.
Regards.
Reply to: