Hey Guys,
As a precursor to my New Year resolutions, I thought I would wire up a blog using Phoenix 1.7 & Beacon CMS.
I ran across an issue related to LiveView version conflict. I have raised an issue over on their Git Repo:
opened 06:51AM - 24 Dec 22 UTC
Hey Guys,
I'm excited about using Beacon CMS in my project.
I just created… a new app using latest release candidate and when I tried to add `{:beacon, github: "beaconCMS/beacon"}` to mix file and ran `mix deps.get`, I got following error:
```elixir
❯ mix deps.get
* Updating beacon (https://github.com/beaconCMS/beacon.git)
origin/HEAD set to main
* Updating safe_code (https://github.com/TheFirstAvenger/safe_code.git)
origin/HEAD set to main
Resolving Hex dependencies...
#Incompatibility<#Term<your app>, cause: {:conflict, #Incompatibility<#Term<not phoenix_live_view 0.18.3 (optional)>, cause: {:conflict, #Incompatibility<#Term<the lock>, #Term<not phoenix_live_view 0.18.3 (optional)>, cause: :dependency>, #Incompatibility<#Term<your app>, #Term<not the lock>, cause: :dependency>}>, #Incompatibility<#Term<your app>, #Term<not phoenix_live_view ~> 0.17.5>, cause: :dependency>}>
Resolution completed in 0.048s
Because "the lock" specifies phoenix_live_view 0.18.3, phoenix_live_view 0.18.3 is required.
So, because your app depends on phoenix_live_view ~> 0.17.5, version solving failed.
** (Mix) Hex dependency resolution failed
```
___
```elixir
❯ elixir --version
Erlang/OTP 25 [erts-13.1.3] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]
Elixir 1.14.2 (compiled with Erlang/OTP 25)
```
Does anyone have a running instance of Beacon CMS?
Do people prefer Nimble Publisher?
jdumont
December 31, 2022, 8:26am
2
Hey! I know you’ve already seen my PR for safe_code
. An extra issue I ran into was running mix tailwind.install
before the mix ecto.reset
task when following the Beacon README.
Other than that, I’ve been able to get Beacon running with Phoenix 1.7. Any questions just shout!
1 Like
Yup, I saw it. Thanks for such a super fast fix!!
I hope it gets merged, I would like to check Beacon out and use it.
Can you also fix the Phoenix Live Storybook not working with Phoenix 1.7rc as well?
I was jus randomly changing paths here and there to make it work.
opened 07:12AM - 31 Dec 22 UTC
I keep seeing these errors:
```elixir
{:phoenix, "~> 1.7.0-rc.0", override: … true},
{:phx_live_storybook, git: "https://github.com/phenixdigital/phx_live_storybook.git"}
```
```elixir
Erlang/OTP 25 [erts-13.1.3] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]
Elixir 1.14.2 (compiled with Erlang/OTP 25)
```
```elixir
(PhxLiveStorybook.AssetNotFound) unknown asset %{"asset" => ["css", "app.css"]}
(phx_live_storybook 0.4.5) lib/phx_live_storybook/controllers/asset_not_found_controller.ex:12: PhxLiveStorybook.AssetNotFoundController.asset/2
(phx_live_storybook 0.4.5) lib/phx_live_storybook/controllers/asset_not_found_controller.ex:1: PhxLiveStorybook.AssetNotFoundController.action/2
(phx_live_storybook 0.4.5) lib/phx_live_storybook/controllers/asset_not_found_controller.ex:1: PhxLiveStorybook.AssetNotFoundController.phoenix_controller_pipeline/2
(phoenix 1.7.0-rc.0) lib/phoenix/router.ex:425: Phoenix.Router.__call__/2
(derpy_portfolio 0.1.0) lib/derpy_portfolio_web/endpoint.ex:1: DerpyPortfolioWeb.Endpoint.plug_builder_call/2
(derpy_portfolio 0.1.0) lib/plug/debugger.ex:136: DerpyPortfolioWeb.Endpoint."call (overridable 3)"/2
(derpy_portfolio 0.1.0) lib/derpy_portfolio_web/endpoint.ex:1: DerpyPortfolioWeb.Endpoint.call/2
(phoenix 1.7.0-rc.0) lib/phoenix/endpoint/sync_code_reload_plug.ex:22: Phoenix.Endpoint.SyncCodeReloadPlug.do_call/4
(plug_cowboy 2.6.0) lib/plug/cowboy/handler.ex:11: Plug.Cowboy.Handler.init/2
(cowboy 2.9.0) /Users/derpycoder/Projects/Web/derpy_portfolio/deps/cowboy/src/cowboy_handler.erl:37: :cowboy_handler.execute/2
(cowboy 2.9.0) /Users/derpycoder/Projects/Web/derpy_portfolio/deps/cowboy/src/cowboy_stream_h.erl:306: :cowboy_stream_h.execute/3
(cowboy 2.9.0) /Users/derpycoder/Projects/Web/derpy_portfolio/deps/cowboy/src/cowboy_stream_h.erl:295: :cowboy_stream_h.request_process/3
(stdlib 4.2) proc_lib.erl:240: :proc_lib.init_p_do_apply/3
```
I see the same error for app.js, fonts.css,



jdumont
December 31, 2022, 8:49am
4
You can just patch it in your local version of safe_code
to trial Beacon without it being merged. Head to /deps/safe_code/mix.exs
and apply the change. Rerunning mix deps.get
(plus the Tailwind install) should get you a running Beacon app.
I’ve not come across Storybook before and don’t have time today to dig into it. Are you only seeing those issues with 1.7? From what I know of the changes I think you might have the same issue with earlier versions too.
1 Like