-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
delay in loader display #22
Comments
This is due to |
Is it better to create a new router hook where we can manually track when the router.push is run |
hi is there an update or fix for this? the delay when using router.push ? |
I don't believe this is possible, because the router.push event only fires once the page has already loaded. Unless you are aware of another way we could implement this. We did, however, just add 2 new funcs with which you can manually start & stop the loader: 'use client';
import { startHolyLoader, stopHolyLoader } from 'holy-loader';
startHolyLoader();
stopHolyLoader(); So you should be able to do: startHolyLoader();
router.push('/your-page') Make sure you are on the latest version (2.3.1) for these to be available. You can run |
hey thanks, after reading the docs, using startHolyLoader(); before router.push works.. thanks a lot |
hi im using
router.push()
from next/navigation. whenever I try to navigate the loader doesn't start on the go.. at the very end of the page load it starts showing.The text was updated successfully, but these errors were encountered: