react-content-loader VS plaiceholder

What's great about is that you can design your loading screens on their site: https://skeletonreact.com/

React Content Loader - SVG-Powered component to easily create placeholder loadings (like Facebook’s cards loading).

This is a Vue port for react-content-loader.

TL;DR; You can reduce the number of queries you make on listing pages by loading content as it gets displayed. Use react-intersection-observer to detect when an element becomes visible and react-content-loader to display a contentful placeholder loader.

I use https://github.com/danilowoz/react-content-loader can create skeletons with svgs. might sound confusing at first but it works well, is performant and does the job. https://skeletonreact.com/ Firstly check this website out see if they already have what you need in their presets

I eventually ended up combining react-intersection-observer and react-content-loader to create a progressive loading experience where elements get loaded as they become visible to users.

The current UX trend is to use some kind of a placeholder animation while loading pieces of UI. react-content-loader is a popular npm package for this use case. It is customizable, supports react and react-native, has some bundled presets, and actually supports SVG animation out of the box.

Because is not a static import, I use a library called plaiceholder to create blurred versions of my images, so I can use placeholder="blur" from Next. Each image is being rendered with different sizes.

So, I have an image component in Next.js I want to add a custom placeholder, I used Plaiceholder to add placeholder, but it only seems to work when the Image has been provided with width and height but does not seem to work when I provide, I manipulate the height and width with CSS .

From my research, I could not find any Next.js package that could help me with the conversion from BlurHash's Base83 data URL to a Base64 data URL, or any Next.js implementation that works for dynamic images. The few packages I found, like the recently published use-next-blurhash and plaiceholder.co, do not work with Next.js for dynamically stored images.

Tip: Plaiceholder is a good tool for generating base64-encoded images.

You might remember that we tried the Plaiceholder library last week, which wasn’t a great success. Since I want to release this project sooner rather than later, I decided to use the same image loading animation as I do on my website.

First, I tried a library called Plaiceholder, to try and see if I could generate Base64 strings to create a blur of all the affiliate programs' images. However, I think generating the Base64 string on the fly for 12 images at a time might be too much to ask since I couldn't get NextJS past the serializing error.

An easy way is to use plaiceholder

What we have done here is a bit of a hack, granted. But it's effective, as all good hacks are. With this, we're setting all placeholder images to be the same data, at least in the context of Storybook. The string above is actually the base64 representation of the placeholder for the plaiceholder example image on their homepage. But we could just as easily upload our own image there and use that.

You can achieve blur-up placeholders with next/image but you have to do some work on the server with either getStaticProps or getServerSideProps using placeholder.