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

@jonathanlurie/nrrdjs

v0.2.4

Published

Pure Javascript NRRD parser for browser and Node

Downloads

1,855

Readme

Pure Javascript NRRD parser for browser and Node

Install

npm install @jonathanlurie/nrrdjs

Usage

EXAMPLE
DOC

Use nrrdjs.parse(...) or await nrrdjs.parseAsync(...) for async/webworker.

The dist/ (umd) and the es/ production build contain both parse() and parseAsync() while the lib/ (cjs) contains only the parse() since it shoul be web worker free to work on Node.

ES6 import can be done like that:

import { parse, parseAsync, Toolbox } from 'nrrdjs'
// ...
parse(...)

or could also be done as such:

import * as nrrdjs from 'nrrdjs'
// ...
nrrdjs.parse(...)

The latter is convenient when in a dual context such as with Nextjs, where import are happening on both the server and the client. Then, importing all makes parseAsync available on client side, while explicitely importing in would crash on server side.

The encoding supported are: raw, ascii and gzip.

In addition to the parser, a toolbox is available under nrrdjs.Toolbox. There, some handy tools are provided:

  • getting the number of components per voxel
  • getting the number of time samples
  • getting slices in the native orthogonal axis
  • getting the voxel-two-world and world-to-voxel matrix
  • getting values in world and voxel coordinates

TODO:

  • Toolbox: better handle time index
  • Toolbox: extract a time volume at a given t

Unsupported:

  • block type (quite unstable from a machine to another)
  • data file/datafile (when the header and the data are contained in two separate files)
  • line skip/lineskip (because applies only to detached headers)
  • byte skip/byteskip (because applies only to detached headers)
  • hexadecimal encoding (when encoding: hex in the header)
  • bzip2 compression