Logger.warn/2 is deprecated

You can resolve that exactly like the warning suggests you to, use Logger.warning/* instead of Logger.warn/*.

You can resolve that exactly like the warning suggests you to, use Logger.warning/* instead of Logger.warn/* .

tks Brother @NobbZ I almost forgot that, perhaps my brain need rest LOL

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.

Tks Brother @garrison for the update news

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…

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.warn will 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.