Question about requirement to use yarn as the engine

[erm-augustinas]

Hi, I've noticed with the latest release yarn has been added to "engines" in package.json. We use yarn 1.22.22 which means the install can't happen unless we use --ignore-engines. Is there any reason for that particular version or even yarn itself to be required for the installation ?

[lookfirst]

Thanks for your report.

To be honest, I want to torch yarn entirely and switch to bun. Yarn started off good, but as soon as they went down this psychotic path of dealing with versions (and what you're dealing with) and downloading files into my repo, they really lost whatever benefits they had.

For another project I just switched to bun and it has been simple, fast and fantastic. When I get some time, I'll do that here or PR's are always welcome if this is a high priority thing.

I'm going to move this to a discussion, since it is a question.

[erm-augustinas]

Thanks for responding @lookfirst . Is it possible for the short term fix to remove "yarn" entry from "engines" field in the package.json?

According to https://docs.npmjs.com/cli/v11/configuring-npm/package-json#engines .

You can also use the "engines" field to specify which versions of npm are capable of properly installing your program.

Is there anything in the current configuration that would break if the user installs using older version of yarn or even npm?