--extra-resource does not accept directories or wildcards anymore

[TimoKunze]

Preflight Checklist

• 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 a bug that matches the one I want to file, without success.

Issue Details

• Electron Packager Version:
  • 19.0.1
• Electron Version:
  • 38.3.0
• Operating System:
  • Windows 11 (24H2)
• Last Known Working Electron Packager version::
  • 18.4.4

Expected Behavior

If the value passed to --extra-resource parameter is a directory instead of a file, the whole directory is copied.

Actual Behavior

If the value passed to --extra-resource parameter (e.g. --extra-resource=out/config) is a directory instead of a file, the command fails with:
Path is a directory: cp returned EISDIR (out/config is a directory (not copied)) out/config

To Reproduce

• Take any project that you package using electron-packager.
• Add a directory out/config with some files and sub-directories.
• Add --extra-resource=out/config to your call of electron-packager.

Additional Information

If we're talking about a low and fixed number of files to copy, it's not a problem to specify --extra-resource for each file individually. But in my case it's a variable number of files and it can easily be several dozen.

[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.

[electron-npm-package-publisher]

🎉 This issue has been resolved in version 19.0.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀