Security News
New Python Packaging Proposal Aims to Solve Phantom Dependency Problem with SBOMs
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
background-image-size-hook
Advanced tools
background-image-size-hook
React hook to get the size of CSS background images.
First npm i background-image-size-hook react react-dom
.
Then when you want to change the dimensions of an element based on the size of its loaded background image:
import { useBackgroundImageSize } from 'background-image-size-hook'
import styled from 'styled-components'
const Box = styled.div`
background-image: url('https://other-domain.com/images/cool.png');
width: ${({ image }) => image.width}px;
height: ${({ image }) => image.height}px;
`
const App = () => {
const [ref, image] = useBackgroundImageSize()
// Use a default while the background image is asynchronously re-loading
const defaultSize = { width: 200, height: 200 }
return <Box ref={ref} image={image ?? defaultSize} />
}
Alternatively, you can hide the element with CSS until the background-image size is known:
const Box = styled.div`
background-image: url('https://other-domain.com/images/cool.png');
display: ${({ image }) => image ? 'block' : 'none'};
width: ${({ image }) => image?.width ?? 200}px;
height: ${({ image }) => image?.height ?? 200}px;
`
const App = () => {
const [ref, image] = useBackgroundImageSize()
return (
<>
<Box ref={ref} image={image} />
{!image && <Skeleton width="200px" height="200px" />}
</>
)
}
Beyond the simple use case of one static background image, more complex use cases require different hook behavior.
If the element has multiple background images then an array of objects will be returned instead of an object. Background images not referenced by a url
will be ignored:
const Box = styled.div`
background-image:
linear-gradient(rgba(0, 0, 255, 0.5), rgba(255, 255, 0, 0.5)),
url('https://other-domain.com/images/cool.png'),
url('data:image/png;base64,iRxVB0…');
`
const App = () => {
const [ref, images] = useBackgroundImageSize()
console.log(images) // Array of two objects for each background image (once loaded)
return <Box ref={ref} />
}
If you use dynamic imports to load background images, for instance gravatars or tenant logos, and use a JavaScript bundler that supports loaders like webpack or esbuild, then you can pass the resolved urls from the imports to the hook, so that the calculation of the background image size is dependent upon changes to the resolved url. This can also be achieved with the mutliple dependencies approach explained below by having the dynamic import state (logo
) as a dependency.
const Box = styled.div`
display: ${({ image }) => (image ? 'block' : 'none')};
background-image: url('${({ image }) => image?.src}');
width: ${({ image }) => image?.width ?? 200}px;
height: ${({ image }) => image?.height ?? 100}px;
`
const App = () => {
const { tenantId } = useContext(Context)
const [logo, setLogo] = useState('')
const [ref, image] = useBackgroundImageSize(logo)
useEffect(() => {
const fetchTenantLogo = async () => {
try {
const logoImport = await import(`./assets/${tenantId}/logo.png`)
setLogo(logoImport.default)
} catch {
setLogo('defaultLogo.svg')
}
}
fetchTenantLogo()
}, [tenantId])
return (
<>
<Box ref={ref} image={image} />
{!image && <Skeleton width="200px" height="100px" />}
</>
)
}
If you want to pass urls from multiple dynamic background images, then use an array but make sure its reference does not change across renders, i.e. it is memoized:
const urls = useMemo(() => [urlA, urlB], [urlA, urlB])
const [ref, images] = useBackgroundImageSize(urls)
If you want to control when the background image size is computed based on other dependencies you can get a reference to the hook's callback by passing true
. In this case the hook will return a callback function that can be called when one of the dependencies changes to get the background image size.
const App = () => {
const [ref, images, getImageSizes] = useBackgroundImageSize(true)
useEffect(() => {
getImageSizes()
}, [getImageSizes, dep1, dep2, etc])
return <Box ref={ref} images={images} />
}
To determine the exact width and height in pixels of the background image, it is reloaded into a dynamic image element (not attached to any DOM tree) which is an asynchronous process. Therefore, in all use cases you must attach the ref
to the element with the background image to help prevent memory leaks, i.e. prevent the hook from potentially calling setState
on an unmounted component. When no URLs are passed to the hook, the ref
is used to get the URL of the background image, in addition to helping prevent a memory leaks.
FAQs
React hook to get the size of a CSS background-image
The npm package background-image-size-hook receives a total of 0 weekly downloads. As such, background-image-size-hook popularity was classified as not popular.
We found that background-image-size-hook demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.