How smapiot/piral works
Main Components
a. Core Framework Layer:
• piral-base as the underlying infrastructure
• piral as the main framework implementation
b. Plugin Architecture:
• Authentication (piral-adal, piral-oauth2, piral-oidc)
• UI Components (piral-dashboard, piral-menu, piral-modals)
• State Management (piral-containers, piral-feeds)
• Utilities (piral-translate, piral-tracking)
c. Converter System:
• Converter architecture supporting multiple frameworks:
• React ecosystem (piral-react, piral-preact)
• Angular (piral-ng)
• Vue (piral-vue, piral-vue-3)
• Other frameworks (piral-svelte, piral-solid, etc.)
d. Development Tooling:
• CLI tools layer (piral-cli)
• Build system (piral-cli-webpack5)
• Debug utilities (piral-debug-utils)
Relationships and Data Flow
a. Core Communication:
• Extension system flow
• Shared dependency management
b. Runtime Flow:
• How pilets are loaded dynamically
• Registration/unregistration process
• Demonstrate state propagation
Implementation Details
• Rectangles: Core components
• Hexagons: Plugins
• Circles: Extension points
• Diamonds: Build/tooling components
• Blue: Core framework
• Green: Plugins
• Orange: Development tools
• Purple: Converters
Additional Elements
a. External Integration:
• Feed service integration
• External dependency management
• Build pipeline integration
b. Development Flow:
• Pilet development lifecycle
• Debug/development environment
• Deployment flow
Notes
Important architectural notes:
• Microfrontend isolation
• Extension capabilities
• Shared resource management
• Debug/development features
• The modular nature of the framework
• The plugin-based architecture
• The multi-framework support
• The development tooling integration
• The runtime flexibility
This system design should help developers understand both the high-level architecture and the detailed component interactions within the Piral framework.