Bug with a hard reload on navigation about awesome-fastapi-projects

[julia-script]

yep, it's related to that, even updating query params messes it up..I had to come up with a hack to work with search params

it only works with search params though, and I didn't implement the scroll flag cause I don't need it

"use client";
import { useSyncExternalStore } from "react";

const isServer = typeof window === "undefined";
class History {
  listeners = new Set<() => void>();

  constructor() {
    if (isServer) {
      return;
    }
    window.addEventListener("popstate", () => {
      this.emit();
    });
  }
  emit() {
    this.listeners.forEach((cb) => cb());
  }
  subscribe = (cb: () => void) => {
    this.listeners.add(cb);
    return () => {
      this.listeners.delete(cb);
    };
  };
  push = (url: string, _: { scroll: boolean }) => {
    if (isServer) {
      return;
    }
    window.history.pushState({}, "", url);
    this.emit();
  };
  replace = (url: string, _: { scroll: boolean }) => {
    if (isServer) {
      return;
    }
    window.history.replaceState({}, "", url);
    this.emit();
  };
  getSnapshot = () => {
    return new URL(window.location.href).searchParams.toString();
  };
}
const customHistory = new History();
export const _useRouter = () => {
  const searchParams = useSyncExternalStore(
    customHistory.subscribe,
    customHistory.getSnapshot,
    () => ""
  );

  return {
    searchParams,
    push: (url: string, options: { scroll: boolean }) => {
      customHistory.push(url, options);
    },
    replace: (url: string, options: { scroll: boolean }) => {
      customHistory.replace(url, options);
    },
  };
};

[vladfedoriuk]

@julia-script Thanks for the input!
I believe a custom history could be a solution for that.
I see there is also some progress on vercel/next.js#48110, so maybe a fix will be delivered shortly in some future release.
I have recently found a package: https://github.com/47ng/next-usequerystate
What caught my eye is: https://github.com/47ng/next-usequerystate#shallow

Note: the app router doesn't vercel/next.js#48110 have this capability natively, but next-usequerystate does, by bypassing the router on shallow updates.

So, I think using this package until a proper fix is introduced in Next.js could be worth trying.