Building priv/static assets for two phoenix apps in one umbrella

Okay, I’ve got this one figured out after reading this StackOverflow post. It’d be awesome if the phx.new.web generator could figure this one out, or perhaps detect the condition and give the developer a clue as to how to proceed.

The generated esbuild and tailwind configs both have a default profile. The new web app requires a different profile under the existing config :esbuild and config :tailwind keys, with a name other than default.

For example:

config :tailwind,
  version: "3.3.2",
  default: [
    args: ~w(
      --config=tailwind.config.js
      --input=css/app.css
      --output=../priv/static/assets/app.css
    ),
    cd: Path.expand("../apps/job_web/assets", __DIR__)
  ],
  internal_ui: [
    args: ~w(
      --config=tailwind.config.js
      --input=css/app.css
      --output=../priv/static/assets/app.css
    ),
    cd: Path.expand("../apps/internal_ui/assets", __DIR__)
  ]

and

config :esbuild,
  version: "0.17.11",
  default: [
    args:
      ~w(js/app.js --bundle --target=es2017 --outdir=../priv/static/assets --external:/fonts/* --external:/images/*),
    cd: Path.expand("../apps/job_web/assets", __DIR__),
    env: %{"NODE_PATH" => Path.expand("../deps", __DIR__)}
  ],
  internal_ui: [
    args:
      ~w(js/app.js --bundle --target=es2017 --outdir=../priv/static/assets --external:/fonts/* --external:/images/*),
    cd: Path.expand("../apps/internal_ui/assets", __DIR__),
    env: %{"NODE_PATH" => Path.expand("../deps", __DIR__)}
  ]

Then, back in the dev.exs config, you have to edit the generated watchers key, replacing default with the key you specified in the tailwind and esbuild configs for the new profile.

If anyone knows of anything else that needs to be done, please reply with additions.

Cheers!

[deleted]