PHPackages                             sourcescript/laravel-dependency-injector - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. sourcescript/laravel-dependency-injector

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

sourcescript/laravel-dependency-injector
========================================

6611[2 issues](https://github.com/SourceScript/LaravelDependencyInjector/issues)PHP

Since Aug 4Pushed 11y ago5 watchersCompare

[ Source](https://github.com/SourceScript/LaravelDependencyInjector)[ Packagist](https://packagist.org/packages/sourcescript/laravel-dependency-injector)[ RSS](/packages/sourcescript-laravel-dependency-injector/feed)WikiDiscussions master Synced today

READMEChangelogDependenciesVersions (1)Used By (0)

\#Laravel Dependency Injector For Laravel4

\###Why? The Effort The hardet part of developing applications which should be scalable in Laravel4 is Dependency Injection. Usually, we always have that nuisance of using `Use \Config` or `Use \Response` on our applications. The big problem would be the impact of implementing this design pattern to development efficiency.

Assuming Laravel 4 just ported and overhauled to a new framework, or imagine you, as a developer switched from using `sentry` to basic `auth`. What do you do? Efficiency and Dependency is always the issue.

\###Version 0.0001 Thanks to the other library, SocialConnect, and two big API-Centric applicaitons that I'm building, There's a big problem w/ dependencies. Now, It would be no issue.

\###Installation

\####Composer ####Facades

```
