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

@coedl/transcription-parsers

v1.4.1

Published

A set of parsers to convert transcription XML files to hierarchical JSON.

Downloads

20

Readme

Transcription Parsers

This is a library for working with linguistic transcriptions. It currently works with eaf, ixt, trs and flextext formats.

It has been designed to work in both browser and node environments. Accordingly, you need to load the file content and pass it to the library. Following are usage examples for both types of environments.

Installation

npm install --save @coedl/transcription-parsers

Browser Usage

Assuming you've loaded the file content over http/s with something like:

const transcriptionPath = `http://{url}/{to}/{transcription.file}
let response = await fetch(transcriptionPath);
if (!response.ok) throw response;
let xmlString = await response.text();```

xml will be the string content that you can then pass to the library viz:

const { Parser } = require("transcription-parser");
let parser = new Parser({
    name: "{name of file.ext}",
    data: xmlString
});
let result = await parser.parse()

NodeJS Usage

Assuming you've loaded the file content with something like:

let xmlString = await fs.readFileSync(
    path.join(__dirname, "{path}/{to}/{file}"),
    "utf-8"
);

xml will be the string content that you can then pass to the library viz:

const { Parser } = require("transcription-parser");
let parser = new Parser({
    name: "{name of file.ext}",
    data: xmlString
});
let result = await parser.parse()