Package: yarnpkg Version: 1.22.10+~cs22.25.14-2 Yarn uses proper-lockfile to implement its `--mutex=file:whatever` option. Its package.json depends on proper-lockfile ^2.0.0, which had the calling convention
lockfile.lock( file, options, callback ) In proper-lockfile 3.0.0 they removed that calling convention in favor of use of promises (much like what happened with mkdirp in bug #972952). This causes yarn's callback to never be called, so yarn does nothing other than print the command name. See, for example, $ yarn init --mutex=file:whatever yarn init v1.22.10 $ -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel