You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some frameworks like Next.js come with the ability to process images on the server side, providing the optimal image based on the current viewport size. When the framework has this tooling available, you can often use images stored either locally or remotely.
Documentation
Working with Images
Image processing with Contentlayer is not currently supported, although we're planning on it. The current recommendation is to place images in the public directory, and then use a string field to store the path to that image.
Alternatively, you can store your images in an asset service like Cloudinary or Imgix. See here for more detail on our current recommendation for image processing.
Using next/image in Body Content
If you want to use next/image to render your images, create a component to wrap next/image and add the image via component markup in your markdown or MDX file.
For example, say we have an Image component in our project that wraps the next/image.
✘ [ERROR] No loader is configured for ".png" files: planetaria-design-system.png
The text was updated successfully, but these errors were encountered: