Using yarn as package manager creates yarn.lock within app even when ignored

[jmquigley]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Changing the package manager to use yarn reproduces the yarn.lock within the app output even when it is ignored. The --ignore will delete the original lock file, but it is then recreated during pruning when yarn install --production --no-bin-links is called in prune.js. Adding the option '--no-lockfile' to this cli call would prevent this behavior (I just modified my local copy of the app to try it). The lock file is not needed for runtime.

[welcome]

👋 Thanks for opening your first issue here! If you have a question about using Electron Packager, read the support docs. If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. Development and issue triage is community-driven, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[malept]

Thanks for catching this. FYI, I'm likely going to drop the --package-manager flag in the next major release (within the next several weeks) so even if I add --no-lockfile in the meantime, it's not going to hang around for much longer.