Skip to content

Latest commit

 

History

History
172 lines (122 loc) · 6.03 KB

README.md

File metadata and controls

172 lines (122 loc) · 6.03 KB

enhance-ssr-elixir-phoenix

If you would like to watch a full video on this, you can do so here:

enhance-elixir

Setup Steps

  1. Install Rust (if not already installed) - run this in a terminal curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
  2. Install elixir - probably just use homebrew
  3. Make sure you have postgres setup and installed - (I use postgresapp.com)

Create a New Phoenix Project (or clone this project)

  • run mix phx.new name_of_app --live
  • You have to give the app a name or it will fail. The --live option is to say this is a LiveView project

Add extism as a dependency

  • in the mix.exs file add {:extism, "1.0.0"}
  • the run mix deps.get

Adding enhance-ssr/wasm

  • Create wasm directory
  • Download the enhance wasm file into local directory - curl -L [https://github.com/enhance-dev/enhance-ssr-wasm/releases/download/v0.0.3/enhance-ssr.wasm.gz](https://github.com/enhance-dev/enhance-ssr-wasm/releases/download/v0.0.3/enhance-ssr.wasm.gz) | gunzip > wasm/enhance-ssr.wasm

A little extra setup (for a basic phoenix project)

  • find your router.ex file under lib/[name_of_project]_web
  • add a new route something similar to live "/enhance", EnhanceLive underneath the get "/"
  • now create a live folder in lib/[name_of_project]_web
  • now create an enhance_live.ex file
  • This will be the module that is responsible for our view when navigating to localhost:4000/enhance

Creating an Extism Plugin

  • Look at extism elixir docs → Show that we need to create a plugin in a very specific way https://extism.org/docs/quickstart/host-quickstart/
  • Create an Elixir/Phoenix module in lib/[name_of_project]_web called SsrWebComponentsOnTheBeam.ConvertComponents that ‘creates_plugin’
defmodule SsrWebComponentsOnTheBeam.ConvertComponents do
    @wasm_plugin_path Path.expand("../../../wasm/enhance-ssr.wasm", __DIR__)

    def create_plugin do
        # Define the path to your local WASM file

        IO.inspect "Creating plugin with path: #{@wasm_plugin_path}"

        # Create the manifest with the local file path
        manifest = %{wasm: [%{path: @wasm_plugin_path}]}

        # Create the plugin with Extism.Plugin.new
        case Extism.Plugin.new(manifest, true) do
          {:ok, plugin} ->
            {:ok, plugin}

          {:error, reason} ->
            {:error, reason}
        end
      end
end
  • Pull up enhance documentation for what enhance expects as a function signature GitHub - enhance-dev/enhance-ssr-wasm: Enhance SSR compiled for WASM

  • Create a ‘call_enhance_plugin’ function

    defmodule SsrWebComponentsOnTheBeam.ConvertComponents do
        @wasm_plugin_path Path.expand("../../../wasm/enhance-ssr.wasm", __DIR__)
    
        def create_plugin do
            # Define the path to your local WASM file
    
            IO.inspect "Creating plugin with path: #{@wasm_plugin_path}"
    
            # Create the manifest with the local file path
            manifest = %{wasm: [%{path: @wasm_plugin_path}]}
    
            # Create the plugin with Extism.Plugin.new
            case Extism.Plugin.new(manifest, true) do
              {:ok, plugin} ->
                {:ok, plugin}
    
              {:error, reason} ->
                {:error, reason}
            end
          end
    
        def call_enhance_plugin(plugin, data) do
          Extism.Plugin.call(plugin, "ssr", Jason.encode!(data))
        end
    end
  • decode the output which should just be a variable called enhance

  • get the document off of the enhance output and return in in a the raw function in a <%= => expression in a ~H template

defmodule SsrWebComponentsOnTheBeam.EnhanceLive do
  use SsrWebComponentsOnTheBeam, :live_view
  use Phoenix.Component

  alias SsrWebComponentsOnTheBeam.ConvertComponents

  def mount(_params, _session, socket) do
    socket =
      socket
      |> assign(:color, "text-red-500")

    {:ok, socket}
  end

  def render(assigns) do
    ~H"""
    <.enhance_header id='my-header' color={@color} />

    <button phx-click="change-color">Change color to red</button>
    """
  end

def enhance_header(assigns) do

    IO.puts "assigns: #{inspect(assigns)}"

    data = %{
        markup: "<my-header id='my-header' color=#{assigns.color}>Hello World</my-header>",
        elements: %{
          "my-header":
            "function MyHeader({ html, state }) {
              const { attrs, store } = state
              const attrs_color = attrs['color']
              const id = attrs['id']
              const store_works = store['readFromStore']
              return html`<h1 class='${attrs_color}'><slot></slot></h1><p>store works: ${store_works} </p><p>attrs id: ${id} </p><p>attrs color: ${attrs_color} </p>`
            }",
        },
        initialState: %{ readFromStore: "true" },
      }

    {:ok, plugin} = ConvertComponents.create_plugin()

    {:ok, output} = ConvertComponents.call_enhance_plugin(plugin, data)

    html = Jason.decode!(output)

    ~H"""
      <div>
        <%= raw(html["document"]) %>
      </div>
    """

  end

  def handle_event("change-color", _, socket) do
    {:noreply, assign(socket, :color, "text-blue-500")}
  end

 end

Checking the output

  • Lastly we want to make sure that we are in fact getting our web components server rendered. So if you navigate to localhost:4000/enhance and inspect the page, you should see something like this.
Screen Shot 2024-06-09 at 12 28 08 PM

If you look at the <my-header></my-header> element, you should see this attribute, enhanced="✨" signifying that you are using the enhance-ssr package to server render your custom elements.

Huzza! Much love to Extism, Enhance, Elixir, and Phoenix Liveview. So many cool things working together.