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

sam-utility

v1.0.4

Published

Sam's commonly-used utilities: HL7 parser, Apache Maven repository cleaner

Downloads

9

Readme

Sam's utilities

HL7 parser

Usage: How to parse a HL7 message

var hl7 = require('sam-utility').hl7;
var objMsg = new hl7.Message(strMsg);

objMsg has a number of properties like:

  • messageType
  • triggerEvent
  • version
  • length (the number of segments)

It also has methods to find segments:

  • findSegment(:segmentName)
  • findAllSegments(:segmentName)
  • filterSegment(:callback) (callback = function(currentSegment, currentIndex) => bool)

How to parse a segment

var segment = new hl7.Segment(str);

segment has the following properties:

  • name
  • length (the number of fields)

It also supports get and set methods:

  • get([fieldIndex, [fieldEntryIndex, [componentIndex, [subComponentIndex]]]])
  • set(newValue, [fieldIndex, [fieldEntryIndex, [componentIndex, [subComponentIndex]]]])

How to parse a field

var field = new hl7.Field(str);

field also supports get and set methods:

  • get([fieldEntryIndex, [componentIndex, [subComponentIndex]]])
  • set(newValue, [fieldEntryIndex, [componentIndex, [subComponentIndex]]])

How to parse a component

var component = new hl7.Component(str);

component also supports get and set methods:

  • get([componentIndex, [subComponentIndex]])
  • set(newValue, [componentIndex, [subComponentIndex]])

sub-component is plain string

Please refer to test/test_hl7.js for more details

Maven cleaner

Usage:

var samUtility = require('sam-utility');
// target-folder, [test or delete], [file-size (1M by default)]
samUtility.DiskCleaner.cleanMaven(process.argv[2], process.argv[3], process.argv[4]);