The order of the formatter include shouldn't matter.
I just tested this locally and it works fine without any errors no matter where the formatter js is located. Unfortunately i can't recreate this issue, maybe if you can provide a link to your page it will be easier to debug.
So the bug is not in the functions. But the order in which Wappler generates the code. With NodeJS, indeed, the order does not matter. A clean restart is enough.
With my projects in PHP/MySQL + includes + routing it's something else.
I code locally for now on a MAMP server.
I restarted several projects several times and with several methods, the results are the same. The environment is more stable with NodeJS.
Unfortunately, I do not want to expose my projects with Javascript derivatives.
My main project is in PHP. When it didn't work, I tried with NodeJS. Look at the beginning.
After restarting several times, the NodeJS project worked.
So, I tried the PHP project right away. And it still didn't work. (Sorry for not mentioning)
And what went wrong this time was the order of dmx-formatter.js ... I think it has to be before all the other functions for PHP projects, especially routing.
I remember this for debugging (before posting):
restart wappler
update the project
try to change the order of insertion of dmx classes
I will prepare a public server for you. But I have already identified some publishing problems... I will first compare if I find the same problems by publishing in ftp before submitting them to you.