Download the PHP package fisharebest/laravel-assets without Composer
On this page you can find all versions of the php package fisharebest/laravel-assets. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 laravel-assets
laravel-assets
Simple, flexible asset management for Laravel 5 - 8. Combine and minify your CSS and JS files to make your website faster.
Installation
Add the dependency to composer.json:
Starting with Laravel 5.5, packages are discovered automatically. For earlier versions, you must add the service provider and facade to config/app.php.
Create a configuration file, config/assets.php, containing default values. Edit the settings in this file to match your project’s directory structure.
Step 1. How to add assets
You would usually add assets in each of your templates (layouts, views, partials, etc.) that requires them.
Of course, you could also add assets anywhere you choose; controllers, helpers, etc.
As well as individual files, you can add named collections of files.
These are defined in config/assets.php.
Where you have dependencies, you should list the files in the order they should be loaded.
For example, if list.js depends on jQuery, you would specify jQuery before list.js.
Duplicates are ignored, so you can add jQuery to each view that uses it and it will only be rendered once.
Step 2. How to render links to assets
It is conventional to render CSS assets in the <head> element, and JS assets at the
end of the <body> element.
But what if…
What if my assets don't have a .js or .css extension?
Specify the type as a parameter when adding the assets. For example,
What if I want to divide my assets into separate groups?
Specify the group as a parameter when adding and rendering assets.
What if I want to add additional attributes to the style/script?
Specify a list of attributes as an argument to the render functions.
What if I my asset files are tiny?
There's a configuration option inline_threshold. Any asset file
smaller than this number of bytes will be rendered inline, thus saving
an HTTP request.
What if I want to change the configuration at runtime?
Configuration can be changed at any time. It only takes effect when the assets are rendered.
What if I want to use my own minifier?
Write your own filter (implement Fisharebest\LaravelAssets\Filters\FilterInterface)
and specify it in the configuration file config/assets.php. Use one of the existing
filters as a template.
What if I want to use a CDN or a cookie-free domain?
Specify a URL in the destination_url setting which corresponds to the folder given
in destination.
What if I need to copy my pipelined assets to an external server?
Write your own notifier (implement Fisharebest\LaravelAssets\Notifiers\NotifierInterface)
and specify it in the configuration file config/assets.php. Use one of the existing
notifiers as a template.
You would most likely set the destination_url to your CDN server, and add a notifier
which copies the file from the destination folder to this server.
What if I cannot use file_get_contents() because of firewall/proxy issues?
Write your own loader (implement Fisharebest\LaravelAssets\Loaders\LoaderInterface)
and specify it in the configuration file config/assets.php. Use one of the existing
loaders as a template.
How do I delete old files after I update my assets or change my filters?
There is an artisan command for that.
All versions of laravel-assets with dependencies
mrclay/minify Version ^3.0.1
tedivm/jshrink Version ^1.3.1
illuminate/support Version 5 - 8
illuminate/contracts Version 5 - 8
illuminate/console Version 5 - 8