1125899906842620 bytes gives the result of 1024 TB because of rounding

I see the only way of solving it – very inelegant corner case management.

        let res = parseFloat((bytes / (1024 ** pow)).toFixed(precision));
        if (res === 1024) {
            res = 1;
            pow++;
        }

[zypA13510]

Without a changelog, the only way to determine if an upgrade is “safe” or not is to look at the commit log, which I was doing. And clearly I failed to understand this change at first look.

I’m not arguing with you whether providing a changelog is a good thing or not, I’m merely giving people (who look for the details of an update, people like me) a better understanding of this issue and that’s it, what’s so wrong about that? This is what I saw, and how I came to this issue, and it only makes me confused because 1125899906842620 is clearly not equal to 1PB. Your test case is even more confusing (to me at least). So that’s why I decided to leave a note to future readers.

Btw, providing a changelog is not that difficult, you may want to look into conventional commits and semantic release

[avoidwork]

https://en.wikipedia.org/wiki/Changelog <— seriously stop being so entitled with the notion of the changelog already, and either land it or stfu.

https://devhints.io/git-log <-- this is required reading