He wanted to get rid of the error, so I told him how to get rid of the error. It changes to a warning, it’s easier to ignore because it’s not bright red when using debuggers.
If you don’t use the debugger to write code, it’s pointless to do anything. I only changed it to a warning for myself so that I could use the console to debug js. I have no idea why so many others care about the errors in this window if they don’t appear in the home assistant logs. If you’re trying to remove these because they appear in the logs, do what I do and ignore all frontend errors & warnings in the logs.
default: error
logs:
requests.packages.urllib3.connectionpool: critical
frontend.js.latest: critical
py.warnings: critical
call it overprotective, I simply don’t like errors or warnings that needn’t be there (or hacks that might trick the system into thinking there is no issue), so I filed the issue here: https://github.com/custom-cards/bar-card/issues/79
Whatever floats your boat. Just don’t get upset when it’s closed with no resolution…
Thanks petro. I just like to fix them as well. Maybe I’m OCD. I open the console often enough for it to piss me off.
Oh i get it. That’s why I hid them all in the logs
It’s only in the console log (F12 in Chrome I see it. Nothing at all in the HA log) but you probably mean ignoring the frontend etc errors… All good.
oh bugger… just noticed this…
2020-05-08 09:45:08 ERROR (MainThread) [hacs] Tried to serve up '/config/www/community/bar-card/index.m.js.map' but it does not exist
2020-05-08 09:46:11 ERROR (MainThread) [hacs] Tried to serve up '/config/www/community/bar-card/index.m.js.map' but it does not exist
hacs error!
Yeah, I believe it’s still an issue with the card and not hacs.