Security News
vlt Debuts New JavaScript Package Manager and Serverless Registry at NodeConf EU
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
gatsby-image
Advanced tools
Lazy-loading React image component with optional support for the blur-up effect.
Speedy, optimized images without the work.
gatsby-image
is a React component specially designed to work seamlessly with Gatsby's GraphQL queries. It combines Gatsby's native image processing capabilities with advanced image loading techniques to easily and completely optimize image loading in your sites.
Huge, unoptimized images dramatically slow down your site.
Creating optimized images for websites has long been a thorny problem. Ideally you would:
Doing this consistantly across a site feels like sisyphean labor. You manually optimize your images and then… several images are swapped in at the last minute or a design-tweak shaves 100px of width off your images.
Most solutions involve a lot of manual labor and bookkeeping to ensure every image is optimized.
This isn't ideal. Optimized images should be the default and very easy.
With Gatsby, we can make images way way better.
gatsby-image
is designed to work seamlessly with Gatsby's native image processing capabilities powered by GraphQL and Sharp. To produce
perfect images, you only need to:
gatsby-image
and use it in place of the built-in img
gatsby-image
.This is what a component using gatsby-images
looks like.
import React from 'react
import Img from 'gatsby-image'
export default ({ data }) => (
<div>
<h1>Hello gatsby-image</h1>
<Img resolutions={data.file.childImageSharp.resolutions} />
</div>
)
export const query = graphql`
query GatsbyImageSampleQuery {
file(relativePath: { eq: "blog/avatars/kyle-mathews.jpeg"}) {
childImageSharp {
# Specify the image processing steps right in the query
# Makes it trivial to update as your page's design changes.
resolutions(width: l25, height: 125) {
...GatsbyImageSharpResolutions
}
}
}
}
`
There are two types of responsive images supported by gatsby-image.
In the first scenario, you want to vary the image's size for different screen resolution -- in other words, create retina images.
For the second scenario, you want to create multiple thumbnails for devices with widths stretching from smartphone to wide desktop monitors and give the browser "hints" about how to choose the right image.
If that sounds complicated, well, it is. But luckily Gatsby does the work, so you don't have to.
Just ask yourself "do I know what size this image will be?" If yes, it's the first type. If no, or you're setting a max-width: 100%;
on your image, then it's the second type.
In Gatsby's GraphQL implementation, you query for the first type by querying a child object of an image called "resolutions" — which you can see in the sample component above. For the second type, you do a similar query but for a child object called "sizes".
GraphQL includes a concept called "query fragments". Which, as the name suggests, are parts of queries that can be reused in multiple queries. To ease building with gatsby-image
, Gatsby image processing plugins which support gatsby-image
ship with fragments which you can easily include in your queries. Note, due to a limitation of GraphiQL, you can not currently use these fragments in the GraphiQL IDE.
Plugins supporting gatsby-image
currently include gatsby-transformer-sharp and gatsby-source-contentful.
Their fragments are:
GatsbyImageSharpResolutions
GatsbyImageSharpResolutions_noBase64
GatsbyImageSharpSizes
GatsbyImageSharpSizes_noBase64
GatsbyContentfulResolutions
GatsbyContentfulResolutions_noBase64
GatsbyContentfulSizes
GatsbyContentfulSizes_noBase64
If you don't want to use the blur-up effect, choose the fragment with noBase64
at the end.
Pass in the data returned from the resolutions
object in your query via the resolutions
prop. e.g. <Img resolutions={resolutions} />
{
imageSharp {
# Other options include height (set both width and height to crop),
# grayscale, duotone, rotate, etc.
resolutions(width: 400) {
# Choose either the fragment including a small base64ed image or one without.
...GatsbyImageSharpResolutions
}
}
}
Pass in the data returned from the sizes
object in your query via the sizes
prop. e.g. <Img sizes={sizes} />
{
imageSharp {
# i.e. the max width of your container is 700 pixels.
#
# Other options include maxHeight (set both maxWidth and maxHeight to crop),
# grayscale, duotone, rotate, etc.
sizes(maxWidth: 700) {
# Choose either the fragment including a small base64ed image or one without.
...GatsbyImageSharpSizes_noBase64
}
}
}
resolutions
— PropTypes.objectsizes
— PropTypes.objectfadeIn
— PropTypes.bool // Defaults to fading in the image on loadtitle
— PropTypes.stringalt
— PropTypes.stringclassName
— PropTypes.oneOfType([PropTypes.string, PropTypes.object]), // Support Glamor's css propstyle
— PropTypes.objectbackgroundColor
— PropTypes.oneOfType([PropTypes.string, PropTypes.bool]) // Set a colored background placeholder. If set to true, uses lightgray
as the color. You can pass in any valid color string.FAQs
Lazy-loading React image component with optional support for the blur-up effect.
The npm package gatsby-image receives a total of 23,622 weekly downloads. As such, gatsby-image popularity was classified as popular.
We found that gatsby-image demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 19 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
Security News
Research
The Socket Research Team uncovered a malicious Python package typosquatting the popular 'fabric' SSH library, silently exfiltrating AWS credentials from unsuspecting developers.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.