ELECTRON_CUSTOM_DIR="v{{ version }}" is not working
See original GitHub issue- Electron-Builder Version: ^22.14.13
- Node Version: v14.18.1
- Electron Version: v16.0.7
- Electron Type (current, beta, nightly): current
- Target: -mw
Problem
Input
ELECTRON_CUSTOM_DIR="v{{ version }}" npx electron-builder -mw
Output
The
"v{{ version }}"
template string not been replaced correctly.
Related issue https://github.com/electron-userland/electron-builder/issues/6445
This bug has been more than a year, I tried to find the source code problem, but I can’t do anything, the code is too deep
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
ng is not recognized as an internal or external command
I solved this problem in accordance with the figure: run in cmd npm install -g @angular/cli. and then. ( open in Windows 10)...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Again, share another better solution
Create a config file
electron-builder-config.js
Edit scripts in
package.json
The idea is that electron-builder.json can be written in
.js
file, so it can access env byprocess.env
object and we can customize the version format as we wish for, but be careful with the config filenameIt’s being used in a upstream library https://github.com/develar/app-builder/blob/c79345743b794ccef41493decafb0b5b2eece505/pkg/electron/electronDownloader.go#L107
AFAICT, it was never made to handle macros, so I don’t think this is really a bug… Regardless, the ticket should be opened against https://github.com/develar/app-builder