Describe the bug 📝

I am using next.js to change pages. when i leave the viewer page i want to disconnect the highlighter and reconnect. I have tried disposing but the isSetup toggle remains true due to that being its default state. when disposing could you make it toggle isSetup to false? Or is there another way to destroy components like highlighter that I should consider? I want to in general keep my obc.components and custom component instances when I page change instead of killing the components instance and rebuild.

the outcome is that i am unable to hook up the event listeners again to the dom object that is created a new when I page change

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 751.36 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.1 - ~/Documents/Local_Repository/nextjs-with-supabase/node_modules/.bin/node
    npm: 10.9.0 - /usr/local/bin/npm
    pnpm: 9.13.2 - /usr/local/bin/pnpm
  Browsers:
    Brave Browser: 130.1.71.123
    Chrome: 131.0.6778.265
    Safari: 17.4.1

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.