# `Lotus.Web.Assets`
[🔗](https://github.com/elixir-lotus/lotus_web/blob/v1.2.0/lib/lotus/web/assets.ex#L1)

Serves the dashboard's CSS and JavaScript bundle.

`Lotus.Web.Router.lotus_dashboard/2` mounts this plug at
`<prefix>/css-<hash>` and `<prefix>/js-<hash>`, where `<hash>` is the MD5 of
the compiled asset. A host never calls it: the URLs come from the layout
through `lotus_asset_path/3`.

The bundle is read and gzipped at compile time, so a response costs no disk
read. Because each URL names the build it came from, the plug answers with
`cache-control: public, max-age=31536000, immutable`, and answers a hash
this build did not produce with a 404 and `cache-control: no-store`.

# `current_hash`

# `stale?`

```elixir
@spec stale?(term()) :: boolean()
```

Whether any of the asset URLs a client is tracking belongs to a previous
build of this bundle.

`tracked` is the `_track_static` list the LiveView client sends on join:
the URLs of every `phx-track-static` tag on the page. Only URLs shaped like
Lotus's own asset routes (`.../css-<hash>` or `.../js-<hash>`) are
considered; the host application's assets are ignored. The dashboard
LiveView uses it to force a full reload after a deploy, since
`Phoenix.LiveView.static_changed?/1` only knows the host's static manifest.

---

*Consult [api-reference.md](api-reference.md) for complete listing*