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

regkey

v2.3.3

Published

Provide fast access to Windows registry for Node.js using native Windows API.

Readme

node-regkey

Introduction

Provide fast access to Windows registry for Node.js using native Windows API.

Install

npm install regkey

If you are using vite, make sure to externalize the regkey from your bundle:

import { defineConfig } from 'vite';

export default defineConfig({
  build: {
    rollupOptions: {
      external: ['regkey']
    }
  },
});

Usage

Import a base key

const { hkcu } = require('regkey')

Open an existing key

try {
  const ms = hkcu.openSubKey('Software/Microsoft')
  ... // do something with ms
} catch (e) {
  if (e instanceof RegKeyError) {
    console.error('Error operating registry: ', e.lastError)
  } else {
    console.error(e.message)
  }
}

Create a new key

const myKey = hkcu.createSubKey('Software/myKey')

If the key already exists, it will be directly opened.

You can also call the RegKey constructor to create a registry key.

const { RegKey, RegKeyAccess } = require('regkey')

const key = new RegKey('HKEY_LOCAL_MACHINE/Software/MyApp')
// specify a remote host and access rights
const key = new RegKey('//MyPC/HKCU/Software/MyApp', RegKeyAccess.Read)

Work with access rights

The RegAccessKey is an enum that specifies the access rights of the key.

You can find the definition of the enum in index.d.ts.

To specify multiple access rights, use | to combine them or put them into an array.

const key = new RegKey('HKEY_CURRENT_USER/Software/MyApp', RegKeyAccess.Read | RegKeyAccess.ia32)
//or
const key = new RegKey('HKEY_CURRENT_USER/Software/MyApp', [RegKeyAccess.Read, RegKeyAccess.ia32])

Get the name of the subkeys

console.log('Subkeys of HKCU/Software/Microsoft:\n', ms.getSubKeyNames())

Close a key

When a RegKey object is released, it automatically closes the attached handle. You can also call close() to manually release the handle.

ms.close()

Use RegKey.valid to check if the key hasn't been closed yet.

if (ms.valid) {
  ... // do something with ms
}

Read values

const values = myKey.values()
for (const value of values) {
  console.log('name: ', value.name)
  console.log('type: ', value.type)
  console.log('value: ', value.value)
  console.log('data: ', value.data, '\n')
}

The value property reads the registry item according to its value type, while data property reads it as a buffer.

Assignments to both of them have the same effect.

You can also call getStringValue to directly get the value as a string.

const value = myKey.getStringValue('some-value')
console.log(value)

Or you can use get function to specify the result type you expect.

const value = myKey.value('some-value').get(String)

The type of value and return value of get function is hard to predict. If you are sure about the type you want, use RegKey.getXxxValue instead. They are faster and more predictable.

Setting values

// directly set
myKey.setStringValue('myValName', 'myValData')
// through RegValue object
myKey.value('myValName').set('myValData')
// specify the type
myKey.value('myValName').set('myValData', RegValueType.REG_SZ)

Delete the key

myKey.deleteTree() // clear values and subkeys
myKey.close() // close the handle (optional, key won't be actually deleted before closed)
parentKey.deleteSubKey(myKey.name) // delete the key