Closed ccinelli closed 5 years ago
It looks like Groupon has done this for all their JS repos that "aren't yarn compatible". They responded to a similar issue opened here https://github.com/groupon/cson-parser/issues/74#issuecomment-438339958.
Maybe @jkrems could shed some more light on the issue. It seems to me, the intent was to stop devs working on their libs with Yarn, but the effect is now consumers of the libs can't use Yarn (or have to ignore-engines
).
My understanding is that package-lock.json
(or yarn.lock
) files are only used when within the package repository, for development of the package itself. When the package is listed as a dependency in some downstream package or application, it's own lockfile is ignored.
Sorry, this kept getting buried in my inbox. I just pushed a change that removes the engines entry. We'll see that we update our automation to deal with this and/or find better ways to signal yarn that it shouldn't be used in this repo.
Any reason why you added this?
If I try to install with
yarn
I get: