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

winreg2

v1.3.3

Published

`winreg2` - A Node.js module allowing access to the Windows Registry by using the built-in `REG.exe`.

Downloads

71

Readme

winreg2

winreg2 - A Node.js module allowing access to the Windows Registry by using the built-in REG.exe.

winreg2 is a fork of the original node-winreg, written in order to support the async/await API and ES modules but designed to be as close to the original API yet lightweight as possible.

Installation

npm install winreg2

Caveats

The original library manually used __defineGetter__ to enforce the read-only on all properties; this is not enforced (but still recommended) in this new library in order to help with console.log messages.

In addition, child_process.exec is used to spawn the REG.exe processes, which may allow for remote code injection and execution (see the Node.js docs page). While winreg2 does rudimentiarily implement some sanitization (encoding all special characters) it is probably incomplete so sanitise all names and values to prevent such vulnerabilities.

Also, there are issues regarding variable expansion: if for example one tries to run the following the output differs from expectation of the expanded value of $HOME (note: as winreg2 uses PowerShell, the variables are denoted with $var and not %var% as in cmd.exe), because winreg2 escapes dollar signs automatically:

await regKey.set("valueName", "$HOME");
console.log(await regKey.get("valueName")); // The string literal "$HOME"

To fix this, replace "$HOME" with process.env.HOME

await regKey.set("valueName", process.env.HOME);
console.log(await regKey.get("valueName")); // should be "C:\\Users\\..."

Finally, exports have been changed. Registry is no longer a default export but rather a named export, while the three enum types (Hive, Arch and RegType) are exported as separate exports instead of being attached as static properties of Registry.

Example

The API is mostly the same except for the Promises being returned instead needing callbacks:

import { Registry, Hive } from 'winreg2';
import { assert } from 'node:assert';
let regKey = new Registry({
    hive: Hive.HKCU,                                        // open registry hive HKEY_CURRENT_USER
    key:  '\\Software\\Microsoft\\Windows\\CurrentVersion\\Run' // key containing autostart programs
});
try{
    let items = await regKey.values();
    items.forEach(item=>{
        console.log(`ITEM: ${item.name}\t${item.type}\t${item.value}`);
    });
}catch(e){
    console.error('Something went wrong:'+  e);
}