
Security News
Open Source Maintainers Feeling the Weight of the EU’s Cyber Resilience Act
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.
electron-webpack
Advanced tools
Configuration and scripts to compile Electron applications that use [electron-vue](https://github.com/SimulatedGREG/electron-vue) boilerplate [project structure](https://simulatedgreg.gitbooks.io/electron-vue/content/en/project_structure.html).
Configuration and scripts to compile Electron applications that use electron-vue boilerplate project structure.
yarn add webpack electron-webpack --dev
And install support for various languages and frameworks — typescript, vue and less if need.
Yarn is recommended instead of npm.
To keep your devDependencies
size minimal, only JavaScript is supported out of the box
(because even in a pure typescript project, JavaScript transpilation is required to import external dependencies on demand (e.g. ui libraries iView, Element)).
Special presets are used to ensure that you don't need to specify all required packages explicitly, — for example, electron-webpack-ts
includes ts-loader
and fork-ts-checker-webpack-plugin
for you.
But if you want, you can install loaders/plugins explicitly (it will be still detected and appropriate config applied).
Supported out of the box. Babel plugins and polyfills that you need based on your used version are determined automatically using babel-preset-env.
yarn add typescript electron-webpack-ts --dev
Create tsconfig.json
in the project root directory:
{
"extends": "./node_modules/electron-webpack/tsconfig-base.json"
}
If you use Vue.js, create vue-shims.d.ts
in the src/renderer
declare module "*.vue" {
import Vue from "vue"
export default Vue
}
yarn add vue electron-webpack-vue --dev
"Import on demand" feature is supported out of the box.
yarn add less-loader less --dev
You can add following scripts to your package.json
:
{
"scripts": {
"dev": "node node_modules/electron-webpack/dev-runner.js",
"compile": "webpack --bail --env.production --config node_modules/electron-webpack/webpack.app.config.js",
"dist": "yarn compile && electron-builder",
"dist-dir": "yarn compile && electron-builder --dir -c.compression=store -c.mac.identity=null"
}
}
yarn dev
Run app in development.yarn compile
Compile app for production. No need to call this script explicitly, only if you want to inspect your compiled app.yarn dist
Build app and package in a distributable format for production.yarn dist-dir
Build app and quickly package in a distributable format for test how does the app work if packed.Webpack documentation is fully applicable. For example, to build for production, specify --env.production
.
node_modules/electron-webpack/webpack.main.config.js
Compile main.node_modules/electron-webpack/webpack.renderer.config.js
Compile renderer.node_modules/electron-webpack/webpack.app.config.js
Compile both main and renderer.All renderer dependencies should be in the devDependencies
. e.g. vue
and vue-router
should be in the devDependencies
.
Because Webpack will smartly copy only required files and as result, application size will be minimal
(electron-builder cannot do such filtering, because in general it is not applicable for node modules).
No doubt, files allows you to filter out anything you want, but it is tedious to write and maintain.
The Dll provide means to split bundles in a way that can drastically improve build time performance.
Supported out of the box, specify in the package.json
:
"electronWebpack": {
"renderer": {
"dll": [
"vue",
"iview/dist/styles/iview.css"
]
}
}
Please note — due to webpack issue, not all libraries are supported for now.
Please see White-listing Externals.
electron-webpack
supports setting this option in the package.json
:
"electronWebpack": {
"whiteListedModules": ["dependency-name"]
}
But keep things simple. electron-compile offers you zero-config setup without predefined project structure and simple on the fly runtime transformation. And for simple projects, even direct usage of typescript
/babel
maybe enough (example).
So, if you doubt what to use and no suitable boilerplate — use electron-compile. If need, later you can easily migrate to webpack.
yarn add source-map-support
and that's all.yarn add webpack-build-notifier --dev
and it will automatically enabled for development.Set the DEBUG environment variable to debug what electron-webpack is doing:
DEBUG=electron-webpack:*
FAQs
> Because setting up `webpack` in the `electron` environment shouldn't be difficult.
The npm package electron-webpack receives a total of 2,293 weekly downloads. As such, electron-webpack popularity was classified as popular.
We found that electron-webpack demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.
Security News
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
Research
/Security News
Undocumented protestware found in 28 npm packages disrupts UI for Russian-language users visiting Russian and Belarusian domains.