npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

electron-named-image

v2.0.0

Published

Node.js bridge to Objective-C [NSImage imageNamed]. Simplifies using default macOS images in Electron apps.

Downloads

26

Readme

This is deprecated because this functionality is now in Electron core.

See https://github.com/electron/electron/pull/10727


electron-named-image

Native node.js addon that returns Objective-C [NSImage imageNamed] calls as a PNG buffer, which simplifies using default macOS images in Electron apps.

Install

npm install electron-named-image

While macOS is currently the only supported platform, this module can be safely installed and used on non-macOS platforms. (No need to wrap your require in a conditional statement or other work-arounds).

What? Why?

This lets you use default macOS images/icons with little effort. So you can set up your TouchBar to look like this:

(Note the macOS TouchBar icons in there in between the defaults)

...or your menu to look like this:

(Note the icons on the menu items)

...without having to manually gather together a bunch of image files. These images/icons are included as a part of macOS and available to Objective-C and Swift via the NSImage API. This module allows you to use it via Javascript.

Sample usage:

new TouchBarButton({
  icon: nativeImage.createFromBuffer(
    namedImage.getImageNamed('NSTouchBarRefreshTemplate')
  )
})
Menu.setApplicationMenu(Menu.buildFromTemplate([
  {
    label: 'My App',
    submenu: [
      { 
        label: 'Empty Trash',
        icon: nativeImage.createFromBuffer(
          namedImage.getImageNamed('NSTrashFull')
        ).resize({ width: 20 })
      }
    ]
  }
]));

For all possible "named images" on macOS, see this.

If you specify an invalid named image or are using it on a macOS version that pre-dates NSTouchBar* icons, you'll get back an empty buffer. For example:

namedImage.getImageNamed('invalid').length // => 0
namedImage.getImageNamed('NSTrashFull').length // => 9166

The empty buffer will work as expected with Electron's nativeImage module, you just won't have any actual image.

All of the NSTouchBar* named images have been outputted as PNGs to the images folder which you can use as well just by manually saving and importing them into your app.

Compiling for use in an Electron app

See [https://github.com/electron/electron/blob/master/docs/tutorial/using-native-node-modules.md] for the easy, right way. Or you can also npm install -g node-gyp and then run the same compile-for-electron script I have in the package.json in the root of this module's folder.

Inspired by https://github.com/electron/electron/issues/9414