mike_bianco
Hello!
New to Elixir & Phoenix. Really incredible work here—thanks for all of the amazing efforts to make an amazing language!
I’m coming from the Ruby & Rails community. Right now, I’m working on upgrading the geoip package to support a more recent version of poison to eliminate a dependency conflict.
In ruby-land, many times you’ll check the version of dependency and modify the package logic to avoid forcing users to upgrade another package to use the latest version of a different package. For example:
if SomeGemName::VERSION > 3.0
do_it_this_way
else
do_it_that_way
end
Here’s the questions I can’t seem to find an answer to:
- I haven’t seen this pattern in the (limited) elixir code I’ve read—is this something that isn’t done in the Elixir community? What’s the best practice here?
- I can’t figure out how to inspect a package version at runtime.
Poison.Mixfile.project[:version]doesn’t seem to be available during runtime and I can’t find any other interfaces to inspect a package version.
Really appreciate everyone’s help here!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
danschultzer
I prefer to either force developers to update their dependencies, or find alternative ways to make the code work independently of the dependency.
In the case of poison requirement, I would guess a better solution would be to just relax requirement in
mix.exs, or make it so geoip doesn’t care whether poison is there, and instead you can switch out the json decoder the same way as in Phoenix and e.g. use jason instead.If I got no other options, then I would do the following (this is from Pow):
I can then check the dependency version requirement like this:
I use the above only in mix tasks or at compile time, since the dependency version is fixed at compile. I wouldn’t do this at runtime.
Last Post!
mike_bianco
@danschultzer thanks for the detailed help here, really appreciate it!
For anyone who runs into the unloaded package issue in the future: the reason why
:poisonwasn’t loaded is because it wasn’t included in the package’s mix.exsapplicationlist. The solution was to removeapplicationaltogether and replace it withextra_applications.