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 🙏

© 2026 – Pkg Stats / Ryan Hefner

apple-plist-utils

v1.0.3

Published

ApplePlistUtils is a collection of utilities for working with Apple's plist format.

Readme

Node.js CI Say Thanks!

ApplePlistUtils

ApplePlistUtils is a collection of utilities for working with Apple's plist format.

Installation

npm install apple-plist-utils --save

Sample Plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<!-- Labels are used to uniquely identify jobs when talking to launchd -->
	<key>Label</key>
	<string>com.example.sampled</string>
	<!-- This array of strings maps one-to-one with your main()'s argv -->
	<key>ProgramArguments</key>
	<array>
		<!-- This assumes sampled is in launchd's PATH -->
		<!-- "launchctl getenv PATH" to check the PATH -->
		<string>sampled</string>
	</array>
	<key>MachServices</key>
	<dict>
		<!-- This key maps to what you pass to bootstrap_look_up() -->
		<!-- Always set the value to true. -->
		<key>com.apple.sampled.something</key>
		<true/>
	</dict>
	<key>Sockets</key>
	<dict>
		<!-- This key is completely up to you. -->
		<!-- Use it to differentiate protocols if your code supports more than one. -->
		<key>SampleListeners</key>
		<dict>
			<!-- This dictionary revolves around getaddrinfo(3) -->
			<!-- Please read up on that API, then look at launchd.plist(5). -->
			<!-- Please also make sure your code can deal with more than one FD being allocated. -->
			<key>SockServiceName</key>
			<string>12345</string>
		</dict>
	</dict>
	<!-- This launchd that we will "check in" -->
	<!-- Checking in with launchd is how we get our file descriptors. -->
	<key>ServiceIPC</key>
	<true/>
</dict>
</plist>

Usage

$ cat index.js 
var utils = require('apple-plist-utils')
var file_path = __dirname + '/test.plist'

console.log(JSON.stringify(utils.parseFile(file_path)))

$ node index.js 
{"?xml":{"@_version":"1.0","@_encoding":"UTF-8"},"plist":{"dict":{"key":["Label","ProgramArguments","MachServices","Sockets","ServiceIPC"],"string":"com.example.sampled","array":{"string":"sampled"},"dict":[{"key":"com.apple.sampled.something","true":""},{"key":"SampleListeners","dict":{"key":"SockServiceName","string":12345}}],"true":""},"@_version":"1.0"}}
$ 
$ cat index.js 
var utils = require('apple-plist-utils')
var file_path = __dirname + '/test.plist'

console.log(JSON.stringify(utils.parseFile(file_path)))

$ cat test.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<!-- Labels are used to uniquely identify jobs when talking to launchd -->
	<key>Label</key>
	<string>com.example.sampled</string>
	<!-- This array of strings maps one-to-one with your main()'s argv -->
	<key>ProgramArguments</key>
	<array>
		<!-- This assumes sampled is in launchd's PATH -->
		<!-- "launchctl getenv PATH" to check the PATH -->
		<string>sampled</string>
	</array>
	<key>MachServices</key>
	<dict>
		<!-- This key maps to what you pass to bootstrap_look_up() -->
		<!-- Always set the value to true. -->
		<key>com.apple.sampled.something</key>
		<true/>
	</dict>
	<key>Sockets</key>
	<dict>
		<!-- This key is completely up to you. -->
		<!-- Use it to differentiate protocols if your code supports more than one. -->
		<key>SampleListeners</key>
		<dict>
			<!-- This dictionary revolves around getaddrinfo(3) -->
			<!-- Please read up on that API, then look at launchd.plist(5). -->
			<!-- Please also make sure your code can deal with more than one FD being allocated. -->
			<key>SockServiceName</key>
			<string>12345</string>
		</dict>
	</dict>
	<!-- This launchd that we will "check in" -->
	<!-- Checking in with launchd is how we get our file descriptors. -->
	<key>ServiceIPC</key>
	<true/>
</dict>
</plist>

$ node index.js 
{"?xml":{"@_version":"1.0","@_encoding":"UTF-8"},"plist":{"dict":{"key":["Label","ProgramArguments","MachServices","Sockets","ServiceIPC"],"string":"com.example.sampled","array":{"string":"sampled"},"dict":[{"key":"com.apple.sampled.something","true":""},{"key":"SampleListeners","dict":{"key":"SockServiceName","string":12345}}],"true":""},"@_version":"1.0"}}

License

MIT License
Copyright (c) 2022 by sakaitaka