# Assets
> Views & assets · Laravel Package Toolkit 2.4.2 · https://package-toolkit.nyoncode.cz/assets/
```php
public function hasAssets(string $directory = 'dist', bool $mirror = true, array $entries = []): static
public function hasViteAssets(array $entries, ?string $base = null): static
```
```php title="src/BlogServiceProvider.php"
$packager
->name('Blog')
->hasAssets(entries: [
'css/blog.css',
'js/blog.js',
]);
```
```text
acme/blog/
└── dist/
├── css/blog.css
└── js/blog.js
```
```blade title="any layout — the package's own, or the application's"
@packageStyles('blog')
@packageScripts('blog')
```
One call gives you four things: two publish tags, a self-maintaining mirror that keeps
`public/vendor/blog` in step with `dist/` without anyone running a command, and tags a template
can ask for by name. [`hasViteAssets()`](#vite-in-the-application) adds the fifth — the same
declaration resolving through the consuming application's own Vite build when that application
wants the package inside it.
## Publishing
```bash
php artisan vendor:publish --tag=blog::assets
php artisan vendor:publish --tag=laravel-assets --force
```
Both tags publish the same files to `public/vendor/{short-name}/`, preserving the directory
structure:
```text
public/vendor/blog/
├── css/blog.css
└── js/blog.js
```
The second tag is the interesting one. `laravel-assets` is what the Laravel application skeleton
already runs from Composer's `post-update-cmd`:
```json title="a Laravel application's composer.json"
"post-update-cmd": [
"@php artisan vendor:publish --tag=laravel-assets --ansi --force"
]
```
It is the same hook Horizon, Telescope and Nova rely on, and it means **one command republishes
every installed package's assets after every `composer update`** — something a per-package tag
cannot express. Laravel accumulates publish groups per path, so registering both tags publishes the
same files and leaves an untagged `vendor:publish` unaffected.
## The asset mirror
Added in 2.3.0, which has since been withdrawn — in practice, available from **2.4**. Publishing
solves the deploy case. The mirror solves the case where nobody published — which, for a package
whose CSS is not optional, is the difference between working and not.
`Support\PublishedAssets` is a container singleton shared by every package in the application. Ask
it for a URL and it returns one, mirroring the package's directory first if anything is missing or
out of date:
```php
use NyonCode\LaravelPackageToolkit\Support\PublishedAssets;
// An og:image the layout composes itself — not a stylesheet or a script, so not
// something a directive renders, and the mirror is how it reaches `public/`.
$url = app(PublishedAssets::class)->url(
'blog',
__DIR__.'/../dist/img/og.png',
);
// https://example.test/vendor/blog/img/og.png?id=1754640000
```
:::note That example is deliberately not a stylesheet
This is the layer, not the way to reach it. A file a template renders as a `` or a `
```
### When `public/` is not writable
A read-only container, Vapor, a hardened deployment. Nothing throws:
```php
$assets = app(PublishedAssets::class);
$url = $assets->url('blog', $path); // null if nothing is published
if ($url === null) {
// Fall back to however you served it before — a CDN, an inline