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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rethinkhealth/hl7v2-lint-no-trailing-empty-field

v0.14.1

Published

hl7v2-lint rule to warn when an empty field (or more) is/are present at the end of a segment

Readme

@rethinkhealth/hl7v2-lint-no-trailing-empty-field

A unified lint rule that warns when an HL7v2 message contains a trailing empty field at the end of a segment.

What is this?

This package validates HL7v2 syntax trees produced by parsers like @rethinkhealth/hl7v2-parser and warns if any segment ends with at least one empty trailing field or more. HL7v2 segments should not end with an extra field separator (|). This rule helps ensure message conformance and prevents subtle bugs in message processing.

When should I use this?

Use this rule to enforce HL7v2 message conformance and catch formatting mistakes that may cause interoperability issues. Trailing field separators are sometimes added by mistake and can lead to parsing errors or misinterpretation by strict receivers.

This linter is useful for:

  • Ensuring HL7v2 segments do not end with unnecessary field separators.
  • Improving message quality and interoperability.
  • Catching formatting mistakes early in development or integration pipelines.

Install

This package is ESM only. In Node.js (v16+), install with npm:

npm install @rethinkhealth/hl7v2-lint-no-trailing-empty-field

Use

On the API:

import { unified } from "unified";
import { hl7v2Parse } from "@rethinkhealth/hl7v2-parser";
import hl7v2LintNoTrailingEmptyField from "@rethinkhealth/hl7v2-lint-no-trailing-empty-field";
import { reporter } from "vfile-reporter";

const msg = `MSH|^~\\&|...`;
const file = await unified()
  .use(hl7v2Parse)
  .use(hl7v2LintNoTrailingEmptyField)
  .process(msg);

console.error(reporter([file]));

API

unified().use(hl7v2LintNoTrailingEmptyField)

Warns when any HL7v2 segment ends with one or more trailing field separators (|).
Reports a message for each segment that violates this rule.

Returns

A unified Transformer that adds warning messages to the file for each segment with a trailing field separator.

Presets

This plugin is included in the following presets:

| Preset | Options | | --------------------------------------- | ------- | | @rethinkhealth/hl7v2-lint-recommended | |

Security

This plugin only transforms AST nodes and does not execute code. Ensure you trust the source of HL7v2 messages before processing.

Contributing

We welcome contributions! Please see our Contributing Guide for more details.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Code of Conduct

To ensure a welcoming and positive environment, we have a Code of Conduct that all contributors and participants are expected to adhere to.

License

Copyright 2025 Rethink Health, SUARL. All rights reserved.

This program is licensed to you under the terms of the MIT License. This program is distributed WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the LICENSE file for details.