Pakowanie wieloplatformowe

When you build an Electron application, you're creating a desktop app using web technologies. To distribute this app to users, you need to package it into an executable or installer specific to their operating system.

Cross-platform packaging means creating these distribution files for Windows, macOS, and Linux from a single codebase. This ensures your app can reach a wide audience regardless of their chosen OS.

electron-builder is the go-to solution for packaging and distributing Electron applications. It's a powerful and flexible tool that automates much of the complex process.

• Generates installers: Creates `.exe`, `.dmg`, `.deb`, `.AppImage`, and more.
• Code signing: Handles signing for security and trust.
• Auto-updates: Integrates with auto-update mechanisms.
• Flexible configuration: Highly customizable through your package.json file or external configuration.

To get started, you'll install electron-builder as a development dependency and add a "build" script to your package.json. This script typically points to the electron-builder command.

Here's a basic setup:

The appId (Application ID) is a crucial identifier for your application. It's a unique string, often in reverse domain name format (e.g., com.yourcompany.yourappname).

• Uniqueness: Helps operating systems identify your app.
• Updates: Essential for distinguishing your app during updates.
• Data storage: Used by OS for application-specific data.

Always use a unique appId for your application.

For Windows, electron-builder can generate different installer types. The most common are NSIS (Nullsoft Scriptable Install System) and Squirrel.Windows.

• NSIS: Creates traditional `.exe` installers, offering more customization.
• Squirrel.Windows: Provides easy auto-updates and a simpler installation experience.

You can define Windows-specific settings under the "win" key in your "build" configuration.

Here's how you might configure `electron-builder` for Windows, specifying targets and an icon:

On macOS, the primary distribution formats are DMG (Disk Image) and PKG (Installer Package). `electron-builder` handles the specifics for these.

• DMG: The most common way to distribute macOS apps, allowing drag-and-drop installation.
• PKG: A traditional installer package, suitable for more complex installations or enterprise distribution.

Crucial macOS settings include category and bundleId (which should match your appId).

This snippet shows macOS-specific settings, including targets, bundle ID, and application category:

Linux has a variety of package formats. electron-builder supports popular ones like AppImage, deb, and rpm.

• AppImage: A universal format that runs on most Linux distributions without installation.
• deb: For Debian-based systems (Ubuntu, Debian).
• rpm: For Red Hat-based systems (Fedora, CentOS).

Similar to macOS, you'll often define a category for your application.

Here's an example of configuring for Linux, targeting different formats and setting an icon:

Match the `electron-builder` target configuration key with its primary operating system.

Great job! You've learned the fundamentals of cross-platform packaging with electron-builder.

• We explored how electron-builder simplifies creating installers for Windows, macOS, and Linux.
• You saw how to configure platform-specific settings directly in your package.json.
• Understanding appId and various installer targets (NSIS, DMG, AppImage) is key to successful distribution.

Next, you'll learn about code signing and notarization, essential steps for ensuring your application is trusted by users and operating systems.