aos VS browserslist

Thank you. The template I bought is using the AOS library. It was a bit challenging to make it work with the App Router, feel free to check my code on how to implement it.

If you’re having trouble seeing the article content, this is the relevant issue:

https://github.com/michalsnik/aos/issues/541

Are you referring to animate on scroll? You can use this library: https://github.com/michalsnik/aos

It's been brought up before: https://github.com/michalsnik/aos/issues/571

I really recommend reading the Github readme or documentation when using a package or library if you hadn't already. (https://github.com/michalsnik/aos)

thank you! not sure which animation you mean but i used the Animate on Scroll to animate them https://github.com/michalsnik/aos

Thanks man, I’m using AOC to do this animations: https://github.com/michalsnik/aos

Maybe https://github.com/michalsnik/aos/issues/574 will help you

Turns out i deployed with vercel and animate on scroll is not working (https://github.com/michalsnik/aos) im thinking it might be a server side rendering issue? Anybody else use this library in conjunction with next.js and might have a solution?

to ourindex.js file. You can also add additional configuration options to the AOS.init() call. See the AOS docs for details.

Not these days, where most people are using evergreen browsers and iOS users upgrade very quickly.

Take a look at the defaults for browserslist, for example:

https://browsersl.ist/#q=defaults

It just barely supports Safari 15, on iOS only, and that’s likely to go away imminently because it’s under 1% usage.

browserslist

We compile JS only for modern browsers. The list of default browsers in Next can be overridden in your browserslist.

In the latest versions of Next.js, targeting specific browsers or features is a breeze using the Browserslist configuration in your package.json file. The latest version of Next.js (v13) uses the following configuration by default:

For a more general answer to browser support, check out https://github.com/browserslist/browserslist. That seems to be standard tool to help you with that.

As someone else pointed out, you're overestimating Chrome/ium's market share.

Regardless, after the web.dev/baseline announcement, I looked at Browslerlist and one of our site's analytics and it is shocking how many people are not using the last two versions of evergreen browsers. There is a long tail of browser versions in those stats.

https://browsersl.ist

The way folks handle this in production is with browserslist, which lets you query on different things you want to support: https://github.com/browserslist/browserslist. This in turn tells other parts of your tooling what language features to transpile for production.

I imagine tools could be built on top of that which do what you’re asking too

# .browserslist.rc # Babel Preset configuration # -------------------------- # Defines web-browser compatibility parameters for Babel to transpile your JS code. # This configuration is used by babel.config.js. # More information in here. # https://github.com/browserslist/browserslist # Support browsers with a market share higher than 5% >10%