Great, now compare it with what I show. Looks like you have generated the project in earlier version of phoenix and migrated it to newest one. You have not done an optional step, see (optional) Update your app to support Phoenix.VerifiedRoutes
Eiji
2
mrbuchmas
Oh yes, you are right. I double-checked and it says version 1.6.15. Which seems strange considering that I thought I generated it with mix phx.new Anyway, I’ve added those things and still get some errors. I’ll post what it looks like below
0
mrbuchmas
Ok, so I followed those steps and now get a new set of errors, not sure what to do from here:
Compiling 8 files (.ex)
error: module Phoenix.VerifiedRoutes is not loaded and could not be found. This may be happening because the module you are trying to load directly or indirectly depends on the current module
lib/drone_shop_web/live/drone_live.ex:2: DroneShopWeb.DroneLive (module)
error: module Phoenix.VerifiedRoutes is not loaded and could not be found. This may be happening because the module you are trying to load directly or indirectly depends on the current module
lib/drone_shop_web/views/error_view.ex:2: DroneShopWeb.ErrorView (module)
error: module Phoenix.VerifiedRoutes is not loaded and could not be found. This may be happening because the module you are trying to load directly or indirectly depends on the current module
lib/drone_shop_web/views/layout_view.ex:2: DroneShopWeb.LayoutView (module)
error: module Phoenix.VerifiedRoutes is not loaded and could not be found. This may be happening because the module you are trying to load directly or indirectly depends on the current module
lib/drone_shop_web/views/page_view.ex:2: DroneShopWeb.PageView (module)
== Compilation error in file lib/drone_shop_web/live/drone_live.ex ==
** (CompileError) lib/drone_shop_web/live/drone_live.ex: cannot compile module DroneShopWeb.DroneLive (errors have been logged)
(elixir 1.15.5) expanding macro: Kernel.use/2
lib/drone_shop_web/live/drone_live.ex:2: DroneShopWeb.DroneLive (module)
expanding macro: DroneShopWeb.__using__/1
lib/drone_shop_web/live/drone_live.ex:2: DroneShopWeb.DroneLive (module)
(elixir 1.15.5) expanding macro: Kernel.use/2
```
0
mrbuchmas
This is what the file looks like now:
@moduledoc """
The entrypoint for defining your web interface, such
as controllers, views, channels and so on.
This can be used in your application as:
use DroneShopWeb, :controller
use DroneShopWeb, :view
The definitions below will be executed for every view,
controller, etc, so keep them short and clean, focused
on imports, uses and aliases.
Do NOT define functions inside the quoted expressions
below. Instead, define any helper function in modules
and import those modules here.
"""
def controller do
quote do
use Phoenix.Controller, namespace: DroneShopWeb
import Plug.Conn
import DroneShopWeb.Gettext
alias DroneShopWeb.Router.Helpers, as: Routes
end
end
def view do
quote do
use Phoenix.View,
root: "lib/drone_shop_web/templates",
namespace: DroneShopWeb
# Import convenience functions from controllers
import Phoenix.Controller,
only: [get_flash: 1, get_flash: 2, view_module: 1, view_template: 1]
# Include shared imports and aliases for views
unquote(view_helpers())
end
end
def live_view do
quote do
use Phoenix.LiveView,
layout: {DroneShopWeb.LayoutView, "live.html"}
unquote(view_helpers())
unquote(html_helpers())
end
end
def live_component do
quote do
use Phoenix.LiveComponent
unquote(view_helpers())
end
end
def component do
quote do
use Phoenix.Component
unquote(view_helpers())
end
end
def router do
quote do
use Phoenix.Router
import Plug.Conn
import Phoenix.Controller
import Phoenix.LiveView.Router
end
end
def channel do
quote do
use Phoenix.Channel
import DroneShopWeb.Gettext
end
end
defp view_helpers do
quote do
# Use all HTML functionality (forms, tags, etc)
use Phoenix.HTML
# Import LiveView and .heex helpers (live_render, live_patch, <.form>, etc)
import Phoenix.LiveView.Helpers
# Import basic rendering functionality (render, render_layout, etc)
import Phoenix.View
import DroneShopWeb.ErrorHelpers
import DroneShopWeb.Gettext
alias DroneShopWeb.Router.Helpers, as: Routes
unquote(verified_routes())
end
end
defp html_helpers do
quote do
# …
# Routes generation with the ~p sigil
unquote(verified_routes())
end
end
def verified_routes do
quote do
use Phoenix.VerifiedRoutes,
endpoint: DroneShopWeb.Endpoint,
router: DroneShopWeb.Router,
statics: DroneShopWeb.static_paths()
end
end
@doc """
When used, dispatch to the appropriate controller/view/etc.
"""
defmacro __using__(which) when is_atom(which) do
apply(__MODULE__, which, [])
end
end
0
sodapopcan
That’s because you ran mix phx.new with version 16 and verified routes did not exist in this version.
If you are in a position where you can start over, you can run mix archive.install hex phx_new which will update your phx_new to use the latest version of Phoenix. Otherwise, just manually update the Phoenix version in your mix.exs and do mix deps.get. You may need to undo the changes you just did first as to avoid a compilation error. You will also probably have to update some other packages as well.
1
Eiji
Module Phoenix.VerifiedRoutes is not available in previous phoenix versions. Therefore I’m now not sure if you really have latest phoenix version …
Here is how it looks like for newly generated project:
$ mix phx.new example
$ mix deps.tree
example
├── ecto_sql ~> 3.10 (Hex package)
├── esbuild ~> 0.7 (Hex package)
├── finch ~> 0.13 (Hex package)
├── floki >= 0.30.0 (Hex package)
├── gettext ~> 0.20 (Hex package)
├── jason ~> 1.2 (Hex package)
├── phoenix ~> 1.7.7 (Hex package)
├── phoenix_ecto ~> 4.4 (Hex package)
├── phoenix_html ~> 3.3 (Hex package)
├── phoenix_live_dashboard ~> 0.8.0 (Hex package)
├── phoenix_live_reload ~> 1.2 (Hex package)
├── phoenix_live_view ~> 0.19.0 (Hex package)
├── plug_cowboy ~> 2.5 (Hex package)
├── postgrex >= 0.0.0 (Hex package)
├── swoosh ~> 1.3 (Hex package)
├── tailwind ~> 0.2.0 (Hex package)
├── telemetry_metrics ~> 0.6 (Hex package)
└── telemetry_poller ~> 1.0 (Hex package)
Could you please compare this with the dependencies you have?
0
mrbuchmas
Alright, the need to update phx_new is definitely helpful information! I think I will do that and make a new project and copy over what I can since I haven’t gone that far into it. I’ll report back on what happens after updating all my dependencies.
0
mrbuchmas
Yes, I was mistaken on the version of Phoenix I was using. I’m going to do generate a new project after updating everything and see if that fixes my issue. I’ll let you know what happens!
1
sodapopcan
Ya, it’s a bit of a hairy command and something that eluded me for a while. It’s one of those things that you run very early on while learning and then completely forget about. It’s also not super intuitive that archive.install will also update an archive. It’s also not too intuitive as to what an “archive” is 
0