The issue with esx_property and esx_status is caused by custom JS clientside script.
How to trace it down:
The easiest method for me was to:
find . -name "__resource.lua" -print0 | xargs -0 grep ".js | grep client
Stop this resource and you will be fine.
Confirmed resources which are breaking the esx_status/property:
Once again, remember it’s about JS file which is defined as client side script. All of the nui js files are fine, as they are just part of the specific resource.
Thanks to @iridium from FiveM’s staff for helping out!