# `mix hakushi.install`
[🔗](https://github.com/hattoriai/hakushi/blob/v0.1.0/lib/mix/tasks/hakushi.install.ex#L1)

Sets up Hakushi in a Phoenix application.

    $ mix hakushi.install
    $ mix hakushi.install --dry-run

The task edits two files:

  * `assets/js/app.js` - adds `import { Hakushi } from "hakushi"` and puts
    `Hakushi` in the `hooks` of the `LiveSocket`. When it cannot find the
    `new LiveSocket(...)` call, or its hooks are not an object or a
    variable, it changes nothing and prints the lines to add.
  * `assets/css/app.css` - adds
    `@import "../../deps/hakushi/priv/static/hakushi.css";`, and the Sumi
    theme import as a comment. The imports follow the deps directory of
    the project (`Mix.Project.deps_path/0`) when it is not `deps/`, as in
    an umbrella child or with `MIX_DEPS_PATH`. For a path dependency
    (`{:hakushi, path: "../hakushi"}`), which Mix does not copy into
    `deps/`, the imports point at the dependency's directory instead.

Then it prints the esbuild note (the app's esbuild must resolve `hakushi`
through `NODE_PATH`: from `deps/`, or, for a path dependency, from the
directory that holds it).

The task is idempotent: it does not add what a file already has, and when
there is nothing to add it says so.

## Options

  * `--dry-run` - prints the changes as a diff and writes nothing.

---

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