I have two questions about popstate.

1. Why is stopImmediatePropagation called here? The popstate event is fired after the pushstate event is fired, so the stopImmediatePropagation is called, will cause the routing switch to fail.

https://github.com/jerrykingxyz/url-change-event/blob/master/src/index.js#L10

2. Why do you need to call history.go when you cancel here?

https://github.com/jerrykingxyz/url-change-event/blob/master/src/index.js#L24

In response to the above two questions, I think the popstate event handling implementation may look like this

window.addEventListener('popstate', function (e) {
    initState();
    const nowIndex = globalWindow.history.state._index;
    const nowURL = new URL(globalWindow.location.href);
    if (nowIndex !== cacheIndex) {
      const notCanceled = globalWindow.dispatchEvent(
        new UrlChangeEvent({
          oldURL: cacheURL,
          newURL: nowURL,
          action: 'popstate',
        }),
      );
      if (!notCanceled) {
        e.stopImmediatePropagation();
      }
      updateCacheState();
    }
  });

When I execute the test through jest, an error is reported here.

Please see how to solve this problem. thanks!

Maybe you can try to upgrade the project dependencies.

While importing this library in angular using import statement, it gives the following error:
'constructor', which lacks return-type annotation, implicitly has an 'any' return type.
constructor(option: IOption)

Following is the PR for solving this issue, please review
#16

In the documentation on npm there is a typo:
'nowURL' instead of 'newURL'