ariandanim
Dear all tim,
I don’t know to solved this warning when try make mix test,
this is the code i get
==> tailwind
Compiling 3 files (.ex)
warning: Logger.warn/1 is deprecated. Use Logger.warning/2 instead
│
72 │ Logger.warn("""
│ ~
│
└─ lib/tailwind.ex:72:14: Tailwind.start/2
warning: Logger.warn/1 is deprecated. Use Logger.warning/2 instead
│
86 │ Logger.warn("""
│ ~
│
└─ lib/tailwind.ex:86:16: Tailwind.start/2
Generated tailwind app
I am using :
- Windows 11
- Elixir 1.16.3
- Phoenix 1.7.12
- Erlang OTP 26
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
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!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
You can resolve that exactly like the warning suggests you to, use
Logger.warning/*instead ofLogger.warn/*.ariandanim
tks Brother @NobbZ I almost forgot that, perhaps my brain need rest LOL
garrison
The warning is from a library (Tailwind).
It was fixed in January and it looks like Jose tagged a release a few days ago but it hasn’t been published to Hex yet for some reason.
You can ignore this warning though, it’s just a deprecation warning. It will be fixed eventually.
ariandanim
Tks Brother @garrison for the update news
NobbZ
Oooof, I assumed this was their own code and just carried that name (
tailwind) coincidally… I usually do not care for warning not from my own code and again assumed no one else did…rhcarvalho
I know what you mean with treating them differently. I go on the cautious side and think when you depend on some code it becomes your code (i.e. need to care about security, correctness, performance, etc of third-party code and how it affects your project).
In this particular case, a call to the deprecated
Log.warnwill only become a real problem once, if ever, the method is removed. The general solution is indeed working with the maintainers of the dependency to have it updated (should be solved in a future release), or if that is not possible you can fork the dependency and fix it in your fork.