Is Weaver still maintained?

No, Scribd has archived Weaver and discontinued support. While the code is available for forking, there are no future updates or bug fixes, making it a risky choice for new projects.

How to set up Weaver in Xcode?

Add a build phase with the 'weaver swift' command before compilation, specifying project and output paths. Install the binary via Homebrew or CocoaPods, and ensure proper configuration as outlined in the README's installation steps.

Weaver vs Swinject: which should I use?

Weaver offers compile-time safety and code generation for reliability, while Swinject is runtime-based and more flexible. Choose Weaver for strict type safety, but note it's deprecated; Swinject is actively maintained and better for dynamic needs.

Can Weaver handle circular dependencies?

Yes, its dependency graph validation detects and prevents circular dependencies at compile time, ensuring the generated code avoids such issues, as mentioned in the features.

Does Weaver work with SwiftUI?

Weaver can be integrated, but its annotation-based approach isn't optimized for SwiftUI's declarative style. You'll need to adapt it manually, as there's no built-in SwiftUI support documented.

What happens if I forget to set up the build phase correctly?

Missing or misordered build phases can cause compilation failures since Weaver won't generate the necessary DI code before compilation, leading to unresolved dependencies and crashes.

Open-Awesome

Weaver

MITSwift1.1.7

A declarative, compile-time safe dependency injection framework for Swift applications on iOS, macOS, and Linux.

Visit Website GitHub

769 stars36 forks0 contributors

What is Weaver?

Weaver is a dependency injection framework for Swift that allows developers to declare dependencies using annotations in code, which it then uses to generate the necessary boilerplate for injection. It solves the problem of managing complex dependency graphs in growing Swift applications by providing compile-time validation and automatic code generation, ensuring that dependencies are resolved safely and efficiently.

Target Audience

Swift developers building iOS, macOS, or Linux applications who need a robust, type-safe way to manage dependencies without resorting to singletons or manual dependency passing.

Value Proposition

Developers choose Weaver because it offers a declarative, compile-time safe approach to dependency injection, eliminating runtime crashes related to dependency resolution and reducing boilerplate code through automatic generation.

Overview

Dependency Injection framework for Swift (iOS/macOS/Linux)

Use Cases

Best For

Managing dependencies in large Swift codebases
Ensuring type safety and non-optional dependency resolution
Automating DI container boilerplate generation
Validating dependency graphs at compile time
Supporting multi-platform Swift projects (iOS/macOS/Linux)
Integrating dependency injection with Objective-C interoperability

Not Ideal For

Projects requiring active maintenance and community support
Teams preferring runtime DI frameworks without code generation overhead
SwiftUI-focused applications needing seamless declarative integration
Environments with strict CI/CD pipelines that avoid deprecated tools

Pros & Cons

Pros

Compile-Time Safety

Validates the entire dependency graph at compile time to prevent runtime crashes from missing or circular dependencies, as emphasized in the README's safety checks.

Automatic Code Generation

Generates DI container boilerplate code automatically, reducing manual setup and errors, demonstrated by the auto-generated resolvers and containers.

Type-Safe Resolution

Resolves dependencies with full type safety and without optionals, ensuring reliable injection, as listed in the key features.

Objective-C Support

Provides compatibility with Objective-C codebases, making it suitable for mixed-language projects, as noted in the features.

Cons

Deprecated and Unsupported

The project is archived with no updates or support, posing risks for long-term use due to potential Swift version incompatibilities and security issues.

Complex Build Phase Setup

Requires a specific Xcode build phase configuration and command-line tool installation, which can be error-prone and adds maintenance overhead, as detailed in the installation section.

Annotation Clutter

Relies on comments or property wrappers for declarations, which can make source code verbose and less readable, especially in large projects.

Frequently Asked Questions

Related Projects

Swinject

Dependency injection framework for Swift with iOS/macOS/Linux

Stars6,707

Forks544

Last commit10 months ago

Typhoon

Powerful dependency injection for Objective-C ✨✨ (https://github.com/appsquickly/pilgrim is the pure Swift successor to Typhoon!!)✨✨

Stars2,692

Forks261

Last commit5 years ago

Needle

Compile-time safe Swift dependency injection framework

Stars2,006

Forks160

Last commit2 months ago

Dip

Simple Swift Dependency container. Use protocols to resolve your dependencies and avoid singletons / sharedInstances!

Stars980

Forks71

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub