Not sure of how to solve this. haven't dig into this one so much yet. maybe anyone else know of any solution.
or maybe it should just be skipped all together in browsers?

it seems to currently be dependent on setting

but only in NodeJS where process exist. it seems to do some magic that i did not know about was a thing that you could do

either way... i live in a timezone with +1 so the result was incorrect with an 1hour offset from the expected result
maybe there is some js solution to encode things to utc if that's the intended format?

anyway. it blocks #1586 for now. don't know if it should be put in as something NodeJS specific.