Getting block location in Scripting after being broken returns invalid values

I was using the stable version of @minecraft/server being 2.4.0.

import { world } from "@minecraft/server";
world.afterEvents.playerBreakBlock.subscribe(({ block }) => {
    console.log(
        JSON.stringify(block.location)
    );
});

To replicate this bug, just start breaking blocks, and you will start noticing coordinates with large numbers being printed in the Content Log GUI (You need to have this enabled). This didn’t happen in previous releases, and it does have some impact on created add-ons.