I imagine this is because serializing an object is not guaranteed to always sort the keys in the same order, but when having the snapshot checked into a repo to compare with then it's a necessity. The final step in our builds is to see if any git tracked files have changed (we're using that instead of the flag in rollup-plugin-size-snapshot because the flag disables the writing of a new file).
I imagine this is because serializing an object is not guaranteed to always sort the keys in the same order, but when having the snapshot checked into a repo to compare with then it's a necessity. The final step in our builds is to see if any git tracked files have changed (we're using that instead of the flag in rollup-plugin-size-snapshot because the flag disables the writing of a new file).
Example: