You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the case of multiple nx-electron projects in a mono-repo, the "dist/executables" folder is the same and so kept getting overridden" upon every "make".
Describe the solution you'd like
A unique folder for each project's executable, perhaps using the projectName (i.e. options.name) of the project being build.
Describe alternatives you've considered
Currently, I resort to modifying the "nx-electron" compiled source upon every installation or upgrade. I.e (0, path_1.join)(options.outputPath, options.name) in the node_modules\nx-electron\src\executors\build\executor.js .
Additional context
And that allows me to get sub-folders within the executable folder for each project.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the case of multiple nx-electron projects in a mono-repo, the "dist/executables" folder is the same and so kept getting overridden" upon every "make".
Describe the solution you'd like
A unique folder for each project's executable, perhaps using the
projectName
(i.e.options.name
) of the project being build.Describe alternatives you've considered
Currently, I resort to modifying the "nx-electron" compiled source upon every installation or upgrade. I.e
(0, path_1.join)(options.outputPath, options.name)
in the node_modules\nx-electron\src\executors\build\executor.js .Additional context
And that allows me to get sub-folders within the executable folder for each project.
The text was updated successfully, but these errors were encountered: