Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure executable output directory. #1041

Closed
3 tasks done
aslilac opened this issue Jul 20, 2019 · 7 comments
Closed
3 tasks done

Configure executable output directory. #1041

aslilac opened this issue Jul 20, 2019 · 7 comments
Assignees
Labels
documentation package Issues related to the `package` command

Comments

@aslilac
Copy link

aslilac commented Jul 20, 2019

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

Currently electron-packager is just always called on a directory named "out". It would be nice if we could control the name of this directory, preferable by just allowing us to set the "out" property for "packagerConfig".

@GrandSchtroumpf
Copy link

Is there any plan concerning this issue ? I'm working in a monorepo with several applications and would be great to be able to specify out path.

@nishant-labs
Copy link

It will be great if anyone could make this happen, really annoying while working in monorepo

@CMCDragonkai
Copy link

This will be really helpful in NixOS, we cannot mutate the input directories inside /nix/store. It's important to set the output directory.

@hadwrf
Copy link

hadwrf commented Jan 13, 2022

I need to modify out directory. It should be configurable.

@jeanbmar
Copy link

jeanbmar commented Feb 8, 2022

PR #2714 submitted, I can't use Electron without this feature either.

@erickzhao erickzhao self-assigned this Mar 16, 2022
@erickzhao erickzhao added package Issues related to the `package` command enhancement labels Nov 1, 2022
dsanders11 pushed a commit that referenced this issue Jan 14, 2023
@Jimbly
Copy link

Jimbly commented Jan 7, 2025

Looks like this issue has been resolved by #3458 and can be closed. As it's not in the docs yet, I'm copying the information from that thread to here for anyone else who finds this issue as the first result on Google =):

Via forge.config.js:

module.exports = {
  outDir: 'my-out-dir',
}

Via package.json:

{
  "config": {
    "forge": {
      "outDir": "my-out-dir"
    }
  }
}

@erickzhao
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation package Issues related to the `package` command
Projects
None yet
Development

No branches or pull requests

8 participants