You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: complete multi-file packaging examples with working implementations
Add comprehensive examples demonstrating four distinct approaches for
packaging WebAssembly components with additional files:
1. Embedded Resources - Files compiled directly into component using
include_str!/include_bytes! macros. Best for small config files
and templates under 1MB. Single signature covers everything.
2. OCI Image Layers - Files accessed from separate container layers
via WASI filesystem APIs. Supports large assets with independent
update cycles and layer-based security.
3. Bundle Archives - Pre-packaged tar/zip archives extracted at
runtime. Ideal for document collections and related file sets
with single deployment artifact.
4. Sidecar Artifacts - Separate OCI artifacts coordinated through
service discovery. Enables multi-team ownership and independent
artifact lifecycles.
Key improvements:
- Fix Rust binding generation issues preventing compilation
- Create working simple_*_test_component examples that build successfully
- Demonstrate filesystem I/O, bundle extraction, and service coordination patterns
- Simplify WIT interface bindings to resolve export macro conflicts
- Add comprehensive documentation and decision matrices
All examples use cross-platform Bazel-native build patterns with
write_file rules instead of shell scripts, ensuring Windows compatibility
and following established project standards.
The multi-file packaging guide provides production-ready patterns for
teams choosing between packaging approaches based on file size, update
frequency, security requirements, and team coordination needs.
0 commit comments