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

sgc

v1.0.0

Published

Synergy configuration file parser

Downloads

3

Readme

node-sgc

An node module to read and write Synergy's configuration file format

This is pretty much only useful if you're writing an interface to Synergy.

Run

  1. Have Node.js

  2. Run npm install in the project directory

  3. Run npm test in the project directory

Usage

Are you writing an interface to Synergy?

Really? Are you sure?

Okay... I mean, if you are writing an interface to Synergy, then this could be very helpful, but chances are you're only continuing reading this because, I suppose, it's more conversational than most README documents.

At any rate, there's SGC.parse and SGC.stringify, mimicking the JSON API.

var SGC = require("SGC");
var fs = require("fs");
var config = SGC.parse(fs.readFileSync("synergy-config.sgc", "utf8"));
console.log(config.screens, config.links, config.aliases, config.options);
fs.writeFileSync("synergy-config.sgc", SGC.stringify(config), {encoding: "utf8"}));

Both functions may throw errors.

Metadata Retention (:lock_with_ink_pen:)

It tries to retain your preferred formatting a bit. It stores the first indentation it finds in config.meta.tab and uses that later if you stringify it.

It also preserves some comments, sometimes in the wrong places.

It can't be perfect. The file changes.

After all, sometimes you don't want it to retain a comment, for example if you change the switch delay, this comment becomes outdated:

switchDelay = 500 # half of a second

I think it would be awesome if someone started work on a comprehensive system for loading, modifying, and saving structured documents while retaining as much metadata and formatting as possible.

∑SYN.Act =∑R-*I(CRed+COOP++AUnimit.)*V(Cust.+Info.)*cc