electron-builder ignores directories named `build` in `files:` configuration

• Version: electron-builder@16.2.1

• Target: Any

create-react-app by default outputs to a directory named build/. With a electron-builder.yml structured like so:

files:
  - electron/
  - node_modules/
  - build/

The build/ directory is excluded. Most likely due to some internal logic.

It’s also unfortunate that setting files: really means asarFiles, and setting it manually overwrites the default values (IE you won’t get node_modules/), and that there’s no equivalent extraAsarFiles.

[lexected]

@mikew God bless your cow, that worked! Thanks for sharing.

So, yes, @develar, as OP mentioned, the directory named “build” does indeed get ignored and has to be explicitly put into “files” option in configuration, like so

"build": {
    "appId": "appid",
    ...
    "files": [
      "scripts/",
      "node_modules/",
      "build/",
      "!node_modules/.cache/",
      "!**/*.map"
    ]
  }

This comes as an issue for most of the people doing a webpack build before packaging the things to be used with electron, and is definitely an issue for anyone who started with create-react-app.

[joeymink]

I don’t see how @develar’s suggestion helps this issue. setting directories.output, say, in package.json like this:

{
  "build": {
    "directories": {
      "output": "custom-output"
    }
  }
}

changes electron-builder’s output folder from the default dist/ to custom-output/. It doesn’t seem to affect the OP’s issue (and my issue at the moment) at all (the build/ folder is still ignored). Might I be missing something?