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

lircd-conf-parser

v0.0.4

Published

Library that parses a LIRCd configuration file

Downloads

3

Readme

Synopsis

This library will parse a lircd.conf file for remotes in Javascript. It should run in both NodeJS and the browser (with browserify).

Installing

npm install lircd-conf-parser

API Reference

  import { default as Parser } from 'lircd-conf-parser';

  fs.readFile('/path/to/lircd.conf', (err, content) => {
    try {
      var parsed = Parser.parse(content);

      parsed.remotes.forEach((remote) => {
        var name = remote.name;

        remote.codes.forEach((code, value) => {
          console.log('LIRC #{code} has the value #{value}');
        });
      });
    } catch(error) {
      console.error("Couldn't parse config file: " + error);
    }
  });

The library supports multiple remotes. Each remote is an object with keys mapping to keys in the config file.

If values in the config file are split by multiple whitespace characters, the additionals characters gets reduced to one space.

Each remote also has multiple codes, which follow the same rules.

The library doesn't validate key names - what ever is stored will be represented.

Tests

npm run test

Contributing

Code does in /src and is cross compiled when the tests are run. Modifications to /lib will be blown away.

If you are going to submit patches, please try to make sure the tests pass, and that you have created a test covering the changes you have made

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2016 Myles Eftos [email protected]

Released under the ISC license. See LICENCE for full details.