wallpaper
Advanced tools
Readme
Get or set the desktop wallpaper
Works on macOS 10.12+, Linux, and Windows 10+.
Maintainer needed for the Linux part of the code. No new Linux-related changes will be accepted until someone with good Linux knowledge volunteers.
$ npm install wallpaper
const wallpaper = require('wallpaper');
(async () => {
await wallpaper.set('unicorn.jpg');
await wallpaper.get();
//=> '/Users/sindresorhus/unicorn.jpg'
})();
Returns a promise for the path of the current desktop wallpaper.
Type: Object
Type: string number
Values: all main or the index of a screen from .screens()
Default: main
The screen to get the wallpaper from.
Returns a promise.
Type: string
The path to the image to set as the desktop wallpaper.
Type: Object
Type: string number
Values: all main or the index of a screen from .screens()
Default: all
The screen to set the wallpaper on.
On Linux and Windows it's hard-coded to main.
Type: string
Values: auto fill fit stretch center
Default: auto
Scaling method.
Returns a promise for the available screens.
(async () => {
await wallpaper.screens();
//=> ['Color LCD']
})();
MIT © Sindre Sorhus
FAQs
Manage the desktop wallpaper
The npm package wallpaper receives a total of 517 weekly downloads. As such, wallpaper popularity was classified as not popular.
We found that wallpaper demonstrated a healthy version release cadence and project activity because the last version was released less than 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
The US Justice Department has penalized two consulting firms $11.3 million for failing to meet cybersecurity requirements on federally funded projects, emphasizing strict enforcement to protect sensitive government data.
Security News
ua-parser-js is set to drop the MIT license and adopt a controversial dual AGPLv3 + PRO licensing model in its upcoming v2.0 release, raising significant concerns among developers and enterprise users.
Security News
Researchers recently demonstrated that the npm Registry is vulnerable to cache poisoning combined with DoS, posing significant risks for package availability.