Electron Desktop App Development · Pelajaran

Pengemasan Lintas Platform

Kuasai opsi dan konfigurasi pengemasan tingkat lanjut menggunakan `electron-builder` untuk distribusi lintas platform yang tangguh.

Pelajaran 1 dari 412 langkah

Pengemasan Lintas Platform adalah pelajaran Electron Desktop App Development gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Electron Desktop App Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

What is Cross-Platform Packaging?

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.

Introducing electron-builder

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.

Basic electron-builder Setup

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:

{
  "name": "my-electron-app",
  "version": "1.0.0",
  "main": "main.js",
  "scripts": {
    "start": "electron .",
    "build": "electron-builder"
  },
  "devDependencies": {
    "electron": "^28.0.0",
    "electron-builder": "^24.0.0"
  },
  "build": {
    "appId": "com.yourapp.id"
  }
}

Understanding "appId"

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.

Windows-Specific Configurations

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.

Windows Config Example

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

{
  "name": "my-electron-app",
  "build": {
    "appId": "com.yourapp.id",
    "win": {
      "target": [
        "nsis",
        "squirrel"
      ],
      "icon": "build/icon.ico"
    }
  }
}

macOS-Specific Configurations

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).

macOS Config Example

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

{
  "name": "my-electron-app",
  "build": {
    "appId": "com.yourapp.id",
    "mac": {
      "target": [
        "dmg",
        "pkg"
      ],
      "category": "public.app-category.developer-tools",
      "bundleId": "com.yourapp.id",
      "icon": "build/icon.icns"
    }
  }
}

Linux-Specific Configurations

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.

Linux Config Example

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

{
  "name": "my-electron-app",
  "build": {
    "appId": "com.yourapp.id",
    "linux": {
      "target": [
        "AppImage",
        "deb",
        "rpm"
      ],
      "category": "Development",
      "icon": "build/icon.png"
    }
  }
}

Check Your Packaging Knowledge

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

Jawab di pelajaran interaktif

Recap & Next Steps

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.

Gratis untuk memulai

Belajar JavaScript dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus: 12
Pelajaran: 47

Mulai belajar gratis Lihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pengemasan Lintas Platform” gratis?

Ya — teks lengkap “Pengemasan Lintas Platform” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Electron Desktop App Development, upgrade ke CoddyKit PRO. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pengemasan Lintas Platform”?

Kuasai opsi dan konfigurasi pengemasan tingkat lanjut menggunakan `electron-builder` untuk distribusi lintas platform yang tangguh. Kamu berlatih Electron Desktop App Development dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Electron Desktop App Development?

Tidak diperlukan pengalaman sebelumnya. Electron Desktop App Development di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Pengemasan Lintas Platform” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Electron Desktop App Development ini?

Ya. Setiap pelajaran Electron Desktop App Development menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Electron Desktop App Development