feat(plugin-history-sync): add history queue context

[orionmiz]

URL navigations not managed in history sync plugin can be ignored when those are executed right after the stackflow actions.

This PR provides a solution about the issue by exposing enqueue function as a hook so that navigations could be inserted into the queue together.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
stackflow-docs	✅ Ready (Inspect)	Visit Preview	Oct 31, 2023 9:54am

[tonyfromundefined]

enqueue() is a raw API-like name that reveals the perception that the inside is a queue, so I wonder if it would be right to expose it to the outside.

I understand that the queue is managed globally, but wouldn't it be better to remove the react dependency and use an API like requestHistoryTick()? (I think there is a better name than this one... If so, please suggest one.)

import { requestHistoryTick } from "@stackflow/plugin-history-sync";

requestHistoryTick(() => {
  console.log("Manipulate history safely here!")
});

Reference interfaces:

• https://nodejs.dev/en/learn/understanding-processnexttick/
• https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame

[orionmiz]

enqueue function cannot be exported as a module since history object is not determined at the module load.
But renaming the function enqueue into requestHistoryTick seems like a great idea 👍

[tonyfromundefined]

LGTM!