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

node-reg

v0.2.4

Published

A simple package for registry interaction from nodejs

Downloads

79

Readme

node-reg

A very simple, and incomplete registry editor for Node.js

Installation

$ npm install --save node-reg

api

Include node-reg in your project

var regedit = require('node-reg');

Currently node-reg only has two methods:

  • addKey
  • getKey

Both take a single object parameter. The expected format for both is:

{
	target: 'Location-in-registry',
	name: 'Name of key',
	value: 'Value for key',
	type: 'The data type'
}

All attributes are necessary in addKey, however only target is necessary for getKey. Name and type are optional for getKey, and value is unused.

Example

var regedit = require('node-reg');

regedit.addKey({
	target: 'HKCU\\Software\\TestDemo',
	name: 'MyApp',
	value: 'heyLookAValue',
	type: 'REG_SZ'
}).then(function(result) {
	console.log(result)
});

regedit.getKey({
	target: 'HKCU\\Software\\TestDemo'
}).then(funciton(result) {
	console.log(result);
});

Notes

  • If a name isn't specified, getKey will return a list of all keys in the target location. If one is specified, it will return the single value (or a message indicating none is available).

TODO

  • Better code documentation
  • Testing
  • Error handling

Version

0.2.0