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

norma43

v1.0.1

Published

Parser TypeScript para ficheros bancarios en formato Norma 43 (AEB-43)

Readme

norma43

TypeScript parser for bank files in Norma 43 (AEB-43) format, the Spanish standard for exchanging current account information.

Features

  • Strict Typing: The output consists of TypeScript objects with well-defined interfaces, with no any.
  • Multiple Input Sources: In-memory string, local file, remote URL, or data stream.
  • Integrated Validation: Detects and reports format errors according to the official specification.
  • Zero Production Dependencies: Lightweight library, no unnecessary overhead.

Installation

pnpm add norma43

Basic Usage

Parse from String

import { parse } from 'norma43';

try {
  const normaFile = parse(norma43String);
  console.log(`Accounts found: ${normaFile.accounts.length}`);
} catch (error) {
  if (error instanceof Norma43ParseError) {
    console.error(`Error in line ${error.lineNumber}: ${error.message}`);
  }
}

Parse from File

import { parseFile } from 'norma43';

const normaFile = await parseFile('./path/to/file.n43');

Parse from URL

import { parseUrl } from 'norma43';

const normaFile = await parseUrl('https://example.com/movements.n43');

Parse from Stream

import { parseStream } from 'norma43';
import { createReadStream } from 'node:fs';

const stream = createReadStream('large-file.n43');
const normaFile = await parseStream(stream);

Data Structure

The parser returns a NormaFile object with the following structure:

  • accounts: Array of Account objects.
    • header: AccountHeaderRecord (Code 11).
    • movements: Array of Movement objects.
      • record: MovementRecord (Code 22).
      • concepts: Array of ConceptComplementaryRecord (Code 23).
      • amountEquivalence: AmountEquivalenceRecord (Code 24, optional).
    • footer: AccountFooterRecord (Code 33).
  • footer: FileFooterRecord (Code 88).

Error Handling

When the parser encounters an invalid format, it throws a Norma43ParseError. This error includes:

  • message: Descriptive error message.
  • code: Error code (e.g., INVALID_LINE_LENGTH, UNKNOWN_RECORD_CODE).
  • lineNumber: Line number where the error occurred (1-indexed).
  • lineContent: Content of the problematic line.

License

MIT