(BROKEN ON MACOS) Binary files lose executable permissions after copy.

[NxRoot]

Binary file execution is completely broken.

This is my code:

new CopyWebpackPlugin({
    patterns: [
      {
        from: path.resolve(__dirname, 'src/main/_py'),
        to: path.resolve(__dirname, '.webpack/main/_py'),
      }
    ]
 })

This will throw an EACCES error every time we try to execute binary files.

The files get copied to the desired folder, however they lose all the permissions to be executed via spawn or exec or any other method to execute them.

I know it is a issue from your plugin because Ive added a delay before executing the files and quickly copied the files manually before they get executed, this way it works but obviously we cant even package the app this way.

I recommend you take a look at this plugin and fix your own plugin.
Thanks

[alexander-akait]

Duplicate of #35, feel free to send a PR, what we need -

If an asset has stats in its assets info, we will apply some stats before write them, we need send a PR to webpack and send PR here to write them (under the option)

[NxRoot]

Duplicate of #35, feel free to send a PR, what we need -

If an asset has stats in its assets info, we will apply some stats before write them, we need send a PR to webpack and send PR here to write them (under the option)

Don't understand what you are saying, it should be an easy fix.
A simple chmod after copying the files would do it...

var file = "PATH/TO/FILE"

// Get current permissions
var stats = fs.statSync(file)
var currentPermission = '0' + (stats.mode & parseInt('777', 8)).toString(8);

// Set permissions on copied files
fs.chmodSync(file, currentPermission)

[alexander-akait]

We can't just run fs.chmodSync here, because writting assets is a part of webpack logic, not a plugin

[NxRoot]

We can't just run fs.chmodSync here, because writting assets is a part of webpack logic, not a plugin

Well, the webpack-permissions-plugin is doing a chmodSync as part of plugin code, how come your copy-webpack-plugin is not able to do it since it is meant to copy files?

I can only understand that from a perspective where you dont want to automatically set permissions, thats ok, but...

Is there any chance of adding a new property to the patterns so that the developer can specify permissions to be applied to the copied files?

[alexander-akait]

Because this plugin is buggy, it uses Node.js fs, but in real usage webpack uses not only Node.js fs, it is possible to use memfs and any other custom fs, this plugin will work for some cases, but it is an invalid solution