-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
not working correctly with Next.js 13.4.19 #834
Comments
NextJS version 13.5 was released short time ago. Does this behaviour still exist on the newest NextJS Version? |
I faced the same issue in next.js version 13+ and I did correctly the installation and It didn't work properly on my end! |
I personally shifted from AOS to animejs which is a far better library to also a bit more complex ... maybe that would be a solution for both of you? :) Keep in mind last commit was October 2018 ... |
I fixed my issue please refer here shadcn-ui/ui#1745 |
same issue in next.js 14.0.4 |
In my case the problem was that all the images were by default lazy loaded. To solve the issue I had to create an Image component that refreshed the AOS as soon as the image finished loading, and then I used this component across the app instead of the next/image one. This is the piece of code that I used: "use client";
import AOS from "aos";
import ImageComponent, { ImageProps } from "next/image";
export function Image(props: ImageProps) {
return (
<ImageComponent
{...props}
onLoad={() => AOS.refresh()}
/>
)
} |
After upgrading project to newest release of nextjs everything stopped working. Not a single element with aos property got rendered (animation was not triggered).
Downgrading it back to 13.4.6 solved the issue
This is:
Specifications
Expected Behavior
Animations should be triggered
Actual Behavior
not a single animation was triggered resulting in unusable website
Steps to Reproduce the Problem
Detailed Description
Possible Solution
The text was updated successfully, but these errors were encountered: