Manually `location.hash = '#some-hash'` call causing page reload and components' `onMounted` lifecycle hook being called again

[Paper-Folding]

Describe the bug

I'm developing a lib that captures hash change event to detect if user clicked back button of browser, if user does, the lib will close all of its modals/dialogs it was created. This is a trick to detect user back button click I found here: https://stackoverflow.com/a/25806609/14963554.
The problem is, this requires a location.hash = #lib call inside lib each time the lib opens a modal/dialog, which I think has conflict with vitepress: each time the location.hash = is called, vitepress reload my custom component and causing onMounted lifecycle hook being fired.

Reproduction

This is the very simple re-production link (please click "Get Started" button to go to reproduction route) :
https://stackblitz.com/edit/vite-m2nugj?file=docs%2Fcomponents%2FCustomComponent.vue

1. First time enter "Get Started" page, an alert message will be called (inside onMounted hook), this is normal;
2. Click the red button, which will cause a location.hash = #lib call, and the alert message show again! This is abnormal! ;
3. Dismiss the alert, click "back button" on browser, (mine is the second button on picture below), and the alert message show yet again! Which means onMounted hook called again! This is abnormal!

Expected behavior

Hash change that does not causing vitepress navigation change should not causing route reload and component restart its lifecycle.

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900HX
    Memory: 21.14 GB / 31.70 GB
  Binaries:
    Node: 18.17.1 - G:\Nodejs\node.EXE
    Yarn: 1.22.19 - G:\Nodejs\yarn.CMD
    npm: 9.6.7 - G:\Nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.2283.0), Chromium (117.0.2045.60)
    Internet Explorer: 11.0.22621.1

Additional context

No response

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

Use history.pushState(null, '', '#foo') instead?

[Paper-Folding]

Use history.pushState(null, '', '#foo') instead?

Thank you for your reply!
The problem actually lies at repeated onMounted hook call when user click the back button to navigate back, not the history.pushState or location.hash = #foo call itself. Even if history.pushState called first or not even being called by my lib, every time user navigates through Vitepress page with the panel on right side, then clicks the back button to navigate back, all components inside a single vitepress page will restart their lifecycle.
And yes, it worked in most cases, as onUnmounted hook will be fired normally, but is it normal to restart all components' lifecycles within a page after user just navigates back without changing a route?