mattstauffer/Torch has 1,864 GitHub stars and 203 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-08 01:08 UTC. Last push 2024-01-27.
Examples of using each Illuminate component in non-Laravel applications
Measured star growth
- in 24h
- 0
- in 7 days
- Update delayed
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
README.md
Original
Torch - Using Laravel's Illuminate Components Independently
Torch is a project to provide instructions and examples for using Illuminate components as standalone components in non-Laravel applications. The current master branch shows how to use Illuminate's 8.0 components.
Note: If you are working with an older project, you might have more success using the 5.5 components or the 5.1 components or the 4.2 components.
Usage
At the moment, the project is divided into many directories beneath components which will each contain an index file, usually written with Slim. Navigate to that directory in your terminal and run the following to serve a web site from that directory:
$ composer install
$ php -S localhost:8000
Now you can visit http://localhost:8000/ in your browser to view the output of each.
Packages
Ready for 8.0
- Artisan Console
- Cache
- Config
- Container
- Database
- Encryption
- Events
- Filesystem
- HTTP Client
- Log
- Middleware
- Pagination
- Queue
- Routing
- Schedule
- Session
- Support
- Translation
- View
- Validation
Need to be moved over from 4.2
- Mail - Never finished porting from 4.2-5.1 and then it never got the simpler upgrades from 5.1 until today
Other Packages
Done
Contributing
A few important notes:
- The imagined end user is a developer of any Symfony-HttpFoundation-using project copying the route closure directly into a project, so try to avoid using any Slim conventions and use as little preparation code outside the closure as possible.
- While some components would be easier to implement with a Laravel-style Application instance and a fuller bootstrap, I'd prefer we implement as many as possible without loading Laravel's Service Providers.
- Some components will require a bootstrap, and I hope we can come up with a Best-Practice bootstrap and Laravel-style Application instance for loading Service Providers, etc.
Contributing
The most helpful use for contributions right now would be updating the readme's in each section to make sure we have instructions on how to test this specific component to see that it's working (based on how the specific index.php for this component is set up).
But my framework doesn't use Symfony's HttpFoundation!
Many of these components will still work. But a few of them require HttpFoundation. ¯\(°_o)/¯
Explore related projects
codecrafters-io/build-your-own-x
Master programming by recreating your favorite technologies from scratch.
561,072 starspublic-apis/public-apis
A collective list of free APIs
497,313 starsmorluto/rea
Reverse engineer anything with agents, from app behavior down to native binaries.
443,622 starsopenclaw/openclaw
The AI that really does things. Any OS. Any Platform. The lobster way. 🦞
394,216 stars