For those finding this thread after running into this error when using Req in a function within a Mix.Task module: This problem is resolved by adding @requirements ["app.start"] at the module level. This ensures that Req and its dependencies are available for use when you execute the Mix task.

More information can be found in the documentation here.

== Compilation error in file lib/cry.ex ==

Oh, you’re using Req at compile-time, i.e. in module body and similar. In that case it seems you need to explicitly start dependencies:

defmodule Foo do
  {:ok, _} = Application.ensure_all_started(:req)
  Req.get(...)
end

compile-time vs runtime is a pretty broad topic so to just scratch the surface when you have a module:

def Foo do
  IO.puts :at_compile_time

  def foo do
    IO.puts :at_runtime
  end
end

the first IO.puts is executed while the module is being compiled. When it is being used at runtime, that IO.puts will not be executed. On the other hand, the second IO.puts is NOT executed when the module is being compiled. It is only executed when you call Foo.foo(). Doing things at compile-time is definitely an Elixir super power and for this particular use case you need that Application.ensure_all_started. (The reason is Req library starts a supervision tree in its application callback module. If it didn’t, ensure_all_started would not be necessary.) In vast majority of day to day Elixir programming, you don’t need ensure_all_started, it is done for you.

I think we have a winner: Tweak Finch supervisor children strartup order by elfenlaid · Pull Request #289 · sneako/finch · GitHub

No, not at all. Modules are loaded just fine but there is the concept of applications that start various OTP processes which is achieved by the applications themselves being “started” (“application” being a useful abstraction here).