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

@httptoolkit/registry-js

v1.9.1-node14

Published

A simple and opinionated library for working with the Windows registry

Downloads

5

Readme

registry-js

A simple and opinionated library for working with the Windows registry

Goals

  • zero dependencies
  • faster than reg.exe
  • implement based on usage - don't replicate the registry API
  • leverage TypeScript declarations wherever possible

Note: This is currently in preview, with support for features that GitHub Desktop and Atom require.

Install

$ npm install --save registry-js
# or
$ yarn add registry-js

But Why?

The current set of libraries for interacting with the registry have some limitations that meant we couldn't use it in GitHub Desktop:

  • windows-registry depends on ffi at runtime, which caused issues with webpack-ing, and was missing APIs we needed.
  • node-winreg depends on reg.exe which breaks as soon as you enable "Prevent access to registry editing tools" Group Policy rules (yes, even QUERY operations are caught by this). More details about this can be found in desktop/desktop#3105.

After exploring other options like invoking PowerShell - which was too slow - we decided to write our own little library to do the stuff we require by invoking the Win32 APIs directly.

Documentation

See the documentation under the docs folder.

Supported versions

Each release of registry-js includes prebuilt binaries for the versions of Node and Electron that are actively supported by these projects. Please refer to the release documentation for Node and Electron to see what is supported currently.

Contributing

Read the Setup section to ensure your development environment is setup for what you need.

This project isn't about implementing a 1-1 replication of the Windows registry API, but implementing just enough for whatever usages there are in the wild.

If you want to see something supported, open an issue to start a discussion about it.