Refresh the browser after making code changes

I'm aware of the refresh workaround, however i was thinking of a fix for the leak by probably getting rid of the useState for the cubes and rendering them imperatively. this should solve the issue and even have better performance since the component no longer rerenders needlessly.
I don't see a good reason to use useState for the shot cubes component.
also right now, the cubeRef is being reset for each rendered cube which doesn't seem correct.

That’s just an example, you can improve it however you like in your app. Another improvement could be using instanced cubes

thanks for the idea, i'm just trying to see what we can do to include good practices as many people will probably use the example as a starting point.

@ErdongChen-Andrew turns out the issue was an incorrect function reference in the event listener