silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Started getting this deprecation notice. Any quick fixes to how my heex stuff is compiled so that this warning goes safely away?
P. S. There is no longer a separate Phoenix section/category, is there?
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Latest Phoenix Threads
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
rhcarvalho
This was an optimization/refactoring in LiveView. The relevant PR is Refactor TagEngine introducing TagEngine.Compiler by SteffenDE · Pull Request #4125 · phoenixframework/phoenix_live_view · GitHub
silverdr
Right… and what am I missing that I get those warnings?
FWIW - I see
Phoenix.LiveView.TagEngine(or evenTagEnginealone) nowhere in the project files. And I get warnings on myheexstuff.steffend
I improved the warning to include the file + line. It could very well be from a dependency. Please try 1.2.5!
silverdr
Thank you. That might help. I’ll check and report.
silverdr
I am sorry it took so long, but – TBH – I got a bit puzzled. I switched to 1.2.5 and… these particular warnings disappeared. Then I spent some time checking whether I might have changed something else but didn’t recall or find anything related. Temporarily rolled back some seemingly unrelated changes but no warnings reappeared. I should have rolled back more and especially LV too, but I had to do some urgent changes and didn’t get back to this until now. All in all - the issue seems to have solved itself, even if I don’t know how
In any case - thank you for your fast reaction.
rhcarvalho
Nice to hear it’s gone without requiring additional work. And if it ever comes back the improved reporting by Steffen will make addressing the issue a precise and hopefully quick task!