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

@xen-orchestra/vmdk

v1.0.0

Published

parse and produce vmdk files

Readme

@xen-orchestra/vmdk

Package Version License PackagePhobia Node compatibility

parse and produce vmdk files

Install

Installation of the npm package:

npm install --save @xen-orchestra/vmdk

Usage

Generate a stream optimized VMDK from any Disk of @xen-orchestra/disk-transform:

import { toVmdkStream } from '@xen-orchestra/vmdk'

const stream = await toVmdkStream(disk, { diskName: 'my-disk.vmdk' })

By default the grain directory and the grain tables are written after the data, like any stream optimized disk: nothing is padded, and the size of the output is only known once it has been fully generated, so stream.length is left undefined.

With the withLength layout, the same grains are followed by a single block of padding, sized so that the file reaches a length computed before anything is generated: stream.length is then the exact size of the output, which an HTTP upload or a tar entry needs in advance — vSphere's HttpNfcLease refuses a chunked body, for instance. It weights the uncompressed size of the allocated grains, plus 0.78%, whatever the content compresses to:

const stream = await toVmdkStream(disk, { layout: 'withLength' })
console.log(stream.length) // exact size of the file

The format itself, and the reading side to come, are described in docs/vmdk.md.

Contributions

Contributions are very welcomed, either on the documentation or on the code.

You may:

  • report any issue you've encountered;
  • fork and create a pull request.

License

ISC © Vates SAS