Download the PHP package smuuf/koloader without Composer
On this page you can find all versions of the php package smuuf/koloader. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download smuuf/koloader
More information about smuuf/koloader
Files in smuuf/koloader
Package koloader
Short Description A lightweight directory-sniffing autoloader with caching.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package koloader
Koloader
Koloader is a super-lightweight directory-sniffing autoloader with caching.
Installation
You probably want to do either of these:
- Direct download or
- With Composer:
composer require smuuf/koloader
Usage
Koloader is created with ease-of-use in mind. Really, you will need only four lines of code in your new project. The rest will be handled for you.
First, include the Koloader in your project
Koloader needs to be included first. If you're not using Composer, this can be done directly by including the Koloader's loader script, which will load everything else that is needed:
And then use it!
The Koloader must be instantiated with a path to an existing temporary directory as an argument:
- Autoloader::__construct(string $pathToTmpDir) - Specified directory will be used for storing cached maps of scanned files. This directory will not be created automatically and thus must exist beforehand.
And then you need to call only two methods on the Koloader instance:
- Autoloader::addDirectory(string $pathToDirectory) - Add a directory to the list of directories that will be scanned for definitions of autoloadable tokens (those good ol' class, interface, trait keywords)
- Autoloader::register() - Call this after all directories were added. This will register the Koloader and from that moment it will handle autoloading.
That is all. Have fun!
