live_svelte/example_project
2026-03-19 12:43:32 -07:00
..
assets feat/add comprehensive e2e testing (#207) 2026-02-18 21:30:17 +02:00
config chore: adjust config for wallaby 2026-03-19 12:43:32 -07:00
lib feat/add comprehensive e2e testing (#207) 2026-02-18 21:30:17 +02:00
priv Upgrade example project. fix remounting Svelte component (#206) 2026-02-08 13:47:39 +02:00
test chore: added svelte encoder 2026-03-19 12:43:32 -07:00
.formatter.exs Add example project 2023-03-14 18:18:15 -07:00
.gitignore Added better navigation between examples projects (#202) 2026-02-01 00:14:15 +02:00
Dockerfile Upgrade example project. fix remounting Svelte component (#206) 2026-02-08 13:47:39 +02:00
mix.exs feat/add comprehensive e2e testing (#207) 2026-02-18 21:30:17 +02:00
mix.lock feat/add comprehensive e2e testing (#207) 2026-02-18 21:30:17 +02:00
README.md chore: adjust config for wallaby 2026-03-19 12:43:32 -07:00

Example

To start your Phoenix server:

  • Run mix setup to install and setup dependencies
  • Start Phoenix endpoint with mix phx.server or inside IEx with iex -S mix phx.server

Now you can visit localhost:4000 from your browser.

Testing

  • Run all tests: mix test (by default this excludes E2E tests; use mix test --only e2e to run browser tests).
  • Run only E2E (browser) tests: mix test --only e2e

E2E test modules must use @moduletag :e2e. E2E tests use Wallaby and serve the app from built assets (priv/static). After changing Svelte (or other frontend) code, rebuild before E2E so tests see your changes:

mix assets.js && mix test --only e2e

Or use the alias (builds assets then runs tests; pass --only e2e to run only E2E):

mix test.e2e --only e2e

You need Chrome and ChromeDriver on your PATH for E2E. If Chromedriver is not installed, run mix test --exclude e2e to run the rest of the suite.

Ready to run in production? Please check our deployment guides.

Learn more