Your problem is that you’re using a function here. The function will be called at runtime, but at runtime the svg’s won’t be available (when using releases) or at least the path might no longer match. You’d want to use a macro, so you read the svg’s content at compile time and only have the result inlined with all the other eex template contents.

I’m definitely missing something - the inline SVG macros above are designed to be used like:

    <button class="btn btn-primary mb2 btn-ple" style='margin-left: 5px' type='submit'>
      #{ Svg.inline("SquareOk") } 
    </button>

(from the code AndyL linked)

But if you’ve got EEx markup that needs to be compiled into a function to return the SVG, it seems like render with an .svg.eex partial should do the right thing:

  <div class="place-where-svg-goes">
    <%= render("my_template.svg", some_param: "foo") %>
  </div>

What about the render approach doesn’t work for your use case?

Your macro:

defmacro inline_svg(file_name) do
  path = static_path(file_name)
  case File.read(path) do
    {:ok, file} -> quote do: {:safe, unquote(file)}
    {:error, _} -> raise "No SVG found at #{path}"
  end
end