Easily use your CSS/JS/etc assets from wherever they are, not just your public directory:
{{-- if you're used to Laravel's asset helper: --}}
<link href="{{ asset('path/to/public/file.css') }}">
{{-- just change asset() to basset() and you can point to non-public files too, for example: --}}
<script src="{{ basset(storage_path('file.js')) }}">
<script src="{{ basset(base_path('vendor/org/package/assets/file.js')) }}">
<script src="{{ basset('https://cdn.com/path/to/file.js') }}">That's all you need to do. Basset will download the file to the predefined disk, then output that disk path to your asset.
Using Basset, you easily internalize and use:
- files from external URLs (like CDNs)
- files from internal, but non-public URLs (like the vendor directory)
- entire archives from external URLs (like GitHub)
- entire directories from local, non-public paths (like other local projects)
No more publishing package files. No more NPM bloat, just to download some files. It's a simple yet effective solution in the age of HTTP/2 and HTTP/3.
composer require backpack/basset
php artisan basset:installTo check that Basset is running correctly, please run:
# recommended - this will tell you if anything is wrong & what to do:
php artisan basset:checkOptionally, you can also publish the config file to make changes in how Basset works:
# optional
php artisan vendor:publish --provider="Backpack\Basset\BassetServiceProvider"The default disk remains basset, which lives under storage/app/public. Run php artisan storage:link so the cached assets are reachable from public/. The installer keeps the command in your composer scripts.
If you prefer to keep cached files under public/ instead of storage/, switch to the public_basset disk (BASSET_DISK=public_basset) and commit or ignore public/basset according to your workflow.
| Disk | Where files live | Pros | Cons |
|---|---|---|---|
basset (default) |
storage/app/public/basset |
Clean git tree; downloads happen on deploy; matches previous defaults | Needs php artisan storage:link; |
public_basset |
public/basset |
Assets are ready to serve after deploy; can be versioned | Git noise unless ignored; |
If you move to public_basset, re-run php artisan basset:install --git-ignore (or edit the file yourself) when you want the installer to append public/basset to .gitignore.
You can just use the basset() helper instead of Laravel's asset() helper, and point to CDNs and non-public files too. Use Laravel's path helpers to construct the absolute path to your file, then Basset will take care of the rest.
For local from CDNs:
{{-- instead of --}}
<link href="{{ asset('path/to/public/file.css') }}">
{{-- you can do --}}
<link href="{{ basset('path/to/public/file.css') }}">
<link href="{{ basset('https://cdn.com/path/to/file.css') }}">
<link href="{{ basset(base_path('vendor/org/package/assets/file.css')) }}">
<link href="{{ basset(storage_path('file.css')) }}">Basset will:
- copy that file from the vendor directory to the basset disk (if needed)
- use the internalized file on all requests
For known asset types like CSS, JS, images and videos, among others, Basset makes it even shorter to load assets. No need to write the HTML for your
+ @endBassetBlock()">+ @bassetBlock('path/or/name-i-choose-to-give-this')
+ @endBassetBlock()