electron-builder | A complete solution to package and build a ready for distribution Electron app with “auto update” su

by electron-userland TypeScript Version: 24.6.3 License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | electron-builder Summary

electron-builder is a TypeScript library typically used in Electron, Debian applications. electron-builder has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

A complete solution to package and build a ready for distribution Electron app with “auto update” support out of the box

Support

Quality

Security

License

Reuse

Support

electron-builder has a medium active ecosystem.

It has 12817 star(s) with 1660 fork(s). There are 150 watchers for this library.

There were 9 major release(s) in the last 12 months.

There are 298 open issues and 5854 have been closed. On average issues are closed in 173 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of electron-builder is 24.6.3

Quality

electron-builder has 0 bugs and 0 code smells.

Security

electron-builder has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

electron-builder code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

electron-builder is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

electron-builder releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 5035 lines of code, 233 functions and 271 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of electron-builder

Get all kandi verified functions for this library.

electron-builder Key Features

No Key Features are available at this moment for electron-builder.

electron-builder Examples and Code Snippets

No Code Snippets are available at this moment for electron-builder.

Community Discussions

Trending Discussions on electron-builder

Vuejs Webpack Compression Plugin not compressing

How to rebuild epoll package in electron?

cannot find module 'sqlite3' after build exe with electron-builder

Docker run bash node: command not found

How to remove cpp files from production build via webpack?

React history & universal-cookie not working in Electron App

How can I enable the cancel button in an electron-built application?

Electron-Prisma Error: can not find module '.prisma/client'

Vue CLI with electron - Unexpected character (1:0) when using native modules

@capacitor-community/electron gives Unhandled Promise Rejection on built package

QUESTION

Vuejs Webpack Compression Plugin not compressing

Asked 2022-Mar-28 at 12:53

I need help debugging Webpack's Compression Plugin.

SUMMARY OF PROBLEM

Goal is to enable asset compression and reduce my app's bundle size. Using the Brotli algorithm as the default, and gzip as a fallback for unsupported browsers.
I expected a content-encoding field within an asset's Response Headers. Instead, they're loaded without the field. I used the Chrome dev tools' network tab to confirm this. For context, see the following snippet:
No errors show in my browser or IDE when running locally.

WHAT I TRIED

Using different implementations for the compression plugin. See below list of approaches:
1. (With Webpack Chain API)

...

ANSWER

Answered 2021-Sep-30 at 14:59

It's not clear which server is serving up these assets. If it's Express, looking at the screenshot with the header X-Powered-By, https://github.com/expressjs/compression/issues/71 shows that Brotli support hasn't been added to Express yet.

There might be a way to just specify the header for content-encoding manually though.

Source https://stackoverflow.com/questions/69288974

QUESTION

How to rebuild epoll package in electron?

Asked 2022-Mar-18 at 11:41

I try to rebuild an electron app but I got this error regarding the epoll installation.

...

ANSWER

Answered 2021-Nov-09 at 06:01

I have a same problem too, but i am using a serialport not epoll.

So, I think the cause of this problem is electron modules not the native module.

Source https://stackoverflow.com/questions/69882740

QUESTION

cannot find module 'sqlite3' after build exe with electron-builder

Asked 2022-Mar-03 at 12:19

I have build my electron app with help of https://medium.com/jspoint/packaging-and-distributing-electron-applications-using-electron-builder-311fc55178d9

it was was success (windows only). but after install published app, i am getting error as shown in screenshort

my scripts as below

package.json

...

ANSWER

Answered 2022-Mar-03 at 12:19

If sqlite3 is required during normal operation of your Electron application and not just during development then you will need to added sqlite3 as a dependency.

IE: Move "sqlite3": "^5.0.2" from "devDependencies": { ... } to "dependencies": { ... }.

package.json

Source https://stackoverflow.com/questions/71265088

QUESTION

Docker run bash node: command not found

Asked 2022-Feb-11 at 10:23

I've the following Dockerfile

...

ANSWER

Answered 2022-Feb-11 at 10:23

When you run bash interactively, your .bashrc file will be run. When you run the command directly on the docker run command, bash is run non-interactively and .bashrc isn't run.

NVM uses .bashrc to set things up, so it needs to run.

You can force bash into interactive mode with the -i option. Then it'll work, but you'll get some warnings because it tries to do some terminal stuff that fails.

Source https://stackoverflow.com/questions/71077832

QUESTION

How to remove cpp files from production build via webpack?

Asked 2021-Dec-25 at 05:32

I use webpack 4 and electron-builder to bundle and build my Electron app. I noticed that native node modules inside the node_modules directory of the app.asar bundle still contain their C++ source files.

Is there a way to exclude certain file extensions from the build step?

...

ANSWER

Answered 2021-Dec-25 at 05:32

electron-builder can exclude files in the files section of your package.json.

Default pattern / is not added to your custom if some of your patterns is not ignore (i.e. not starts with !). package.json and /node_modules// (only production dependencies will be copied) is added to your custom in any case. All default ignores are added in any case — you don’t need to repeat it if you configure own patterns.

Example

Source https://stackoverflow.com/questions/70431250

QUESTION

React history & universal-cookie not working in Electron App

Asked 2021-Dec-12 at 23:34

I'm currently carrying over a web project over to Electron, with the use of ReactJs, Redux, Express, MongoDB & Tailwind. I'm currently stuck on my authentication, where previously I made use of universal-cookies and history.push() for the usual redirecting and validation of cookies for the authentication process. Everything works perfectly fine, when I'm in the development server. I can see the cookies being added and redirection is working as expected. Now when I build the application, I try to login in, but nothing happens at all, but I can see the login request being successfully sent from the express server. I'm unsure if cookies are supported in Electron or either the use of history.push() (react-router-dom), but it's just odd seeing it work in the development server. Any help would be appreciated.

ANSWER

Answered 2021-Dec-12 at 23:34

Well I've just realised, coding long periods of time can cause a person to make the simplest mistakes. Well I figured that in order for the electron app to run after the build, the client server is still needed... so the only think that had to be done was to make use write a simple script, to ensure the backend is executed as well as executing the front-end server in order for the actual build to work.

Source https://stackoverflow.com/questions/70328001

QUESTION

How can I enable the cancel button in an electron-built application?

Asked 2021-Nov-30 at 00:39

I'm working with an electron application that is built via electron-builder. When I generate the installer and begin installing with it, I see that the cancel button is disabled.

I've looked around at some electron builder documentation and done a few google searches but I seem to be coming up blank here.

edit: Discovered that I can use build/installer.nsh to actually modify UI elements, now I'm just wondering, how do I gain access to the button to enable / disable it, the examples I've seen use an .ini file to store options or something similar, but I'm getting recommendations to use nsDialogs.

Is nsDialogs something that's already readily accessible to me or do I need to import something into my installer.nsh file to use nsDialogs?

And by that token, how would I access the cancel button in nsDialogs?

Is there a configurable value that enables me to... enable that cancel button so users can choose to cancel during installation?

Thanks!

...

ANSWER

Answered 2021-Nov-30 at 00:39

NSIS installers do not support canceling the installation when you enter the InstFiles page (or any page after it). This is by design because of how the scripting language works.

If you don't mind hacks you can call the uninstaller when the user clicks cancel during the install phase:

Source https://stackoverflow.com/questions/70101420

QUESTION

Electron-Prisma Error: can not find module '.prisma/client'

Asked 2021-Nov-20 at 12:10

I'm building a Nuxt-electron-prisma app and I kinda stuck here. when I use prisma normally as guided every thing is fine on dev but on build i get this error :

...

ANSWER

Answered 2021-Sep-26 at 06:51

Ok, I finally solved it!! first of all no need to change client generator output direction!

Source https://stackoverflow.com/questions/69323946

QUESTION

Vue CLI with electron - Unexpected character (1:0) when using native modules

Asked 2021-Oct-29 at 21:51

In some popular NodeJS libraries, e.g. ssh2 or node-pty, there is natively compiled code as part of the library. Creating the project with

...

ANSWER

Answered 2021-Oct-29 at 21:51

One solution I found is this:

Add yarn add -D native-ext-loader (my version is 2.3.0 and electron is at 13.x)
Adjust vue.config.js and add the chainWebpackMainProcess like this:

Source https://stackoverflow.com/questions/69775139

QUESTION

@capacitor-community/electron gives Unhandled Promise Rejection on built package

Asked 2021-Oct-03 at 18:22

When I pack my Ionic project with @capacitor-community/electron packager (using electron-builder), I get the following error:

...

ANSWER

Answered 2021-Oct-03 at 18:22

So, apparently problem lies in default publish method. You need to change your electron-builder.config.json file to the following form (without the comment):

Source https://stackoverflow.com/questions/69427673

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install electron-builder

Yarn is strongly recommended instead of npm.
electron-webpack-quick-start is a recommended way to create a new Electron application. See Boilerplates. Please note that everything is packaged into an asar archive by default. For an app that will be shipped to production, you should sign your application. See Where to buy code signing certificates.
Specify the standard fields in the application package.json — name, description, version and author.
Specify the build configuration in the package.json as follows: "build": { "appId": "your.id", "mac": { "category": "your.app.category.type" } } See all options. Option files to indicate which files should be packed in the final application, including the entry file, maybe required.
Add icons.
Add the scripts key to the development package.json: "scripts": { "app:dir": "electron-builder --dir", "app:dist": "electron-builder" } Then you can run yarn app:dist (to package in a distributable format (e.g. dmg, windows installer, deb package)) or yarn app:dir (only generates the package directory without really packaging it. This is useful for testing purposes). To ensure your native dependencies are always matched electron version, simply add script "postinstall": "electron-builder install-app-deps" to your package.json.
If you have native addons of your own that are part of the application (not as a dependency), set nodeGypRebuild to true.