Question 1

Inertia.js Phoenix adapter vs Phoenix LiveView: which should I choose?

Accepted Answer

Choose Inertia.js if you want to use React, Vue, or Svelte with a SPA-like feel and server-driven pages. Pick LiveView for full server-side rendering with minimal JavaScript and real-time updates via WebSockets, without a separate frontend framework.

Question 2

How to set up server-side rendering with Inertia.js in Phoenix?

Accepted Answer

Create an SSR JavaScript file (e.g., ssr.jsx), configure esbuild for it, add Inertia.SSR to your supervision tree, and enable SSR in config. Requires Node.js installation and setting NODE_ENV=production for caching, as per the README.

Question 3

Does the Inertia.js Phoenix adapter work with TypeScript?

Accepted Answer

Yes, the Igniter installer supports a --typescript flag for TypeScript configuration, and you can manually set up TypeScript in your assets, though the README focuses on JavaScript examples.

Question 4

How do I handle form validation errors with Ecto changesets?

Accepted Answer

Use the assign_errors helper in controllers to pass Ecto changeset errors to the frontend; it automatically flattens nested errors into a format compatible with Inertia's form helpers.

Question 5

What's the performance impact of using deferred props?

Accepted Answer

Deferred props load expensive data asynchronously after the initial page render, improving perceived performance by reducing initial payload size, but they require client-side async requests which can add latency.

Question 6

Can I use this adapter with pagination libraries like Scrivener?

Accepted Answer

Yes, via the scroll props feature or custom ScrollMetadata protocol implementation, allowing integration with pagination data structures for infinite scroll interfaces.

Phoenix

What is Phoenix?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions