@_traeop_/electron-modular 1.0.8 → 1.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
## Overview
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
A lightweight dependency injection container for Electron's main process that brings modular architecture and clean code organization to your desktop applications.
|
|
6
|
+
|
|
7
|
+
### What It Solves
|
|
8
|
+
|
|
9
|
+
Building complex Electron apps often leads to tightly coupled code, scattered IPC handlers, and difficulty managing window lifecycles. This package addresses these challenges by providing:
|
|
10
|
+
|
|
11
|
+
- **Organized Code Structure** - Split your application into independent, testable modules instead of monolithic files
|
|
12
|
+
- **Automatic Dependency Management** - No more manual service instantiation or passing dependencies through multiple layers
|
|
13
|
+
- **Centralized IPC Logic** - Group related IPC handlers with their business logic instead of scattering them across your codebase
|
|
14
|
+
- **Window Lifecycle Control** - Manage BrowserWindow creation, caching, and event handling in dedicated classes
|
|
15
|
+
- **Type-Safe Module Boundaries** - Share only necessary interfaces between modules using the provider pattern
|
|
16
|
+
|
|
17
|
+
### What You Get
|
|
18
|
+
|
|
19
|
+
The package uses TypeScript decorators (`@RgModule`, `@Injectable`, `@IpcHandler`, `@WindowManager`) to eliminate boilerplate and let you focus on business logic. Services are automatically instantiated with their dependencies, IPC handlers are registered during module initialization, and windows are created with lifecycle hooks that run at the right time.
|
|
20
|
+
|
|
21
|
+
Instead of wrestling with service initialization order or managing global state, you define modules with clear dependencies and let the container handle the rest.
|
|
6
22
|
|
|
7
23
|
### Key Features
|
|
8
24
|
|
package/package.json
CHANGED