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

@qgustavor/las-reader

v2.0.3

Published

Read LAS lidar point clouds

Readme

@qgustavor/las-reader

Read LAS lidar point clouds in Node.js and the browser.

npm install @qgustavor/las-reader

Node.js 24 or newer. ESM only.

Quick start

import { openFile } from '@qgustavor/las-reader/node'

const reader = await openFile('cloud.las')

console.log(reader.header.versionString, reader.pointCount)

for await (const point of reader) {
  console.log(point.x, point.y, point.z, point.classification)
}

await reader.close()

In a browser, open a file the user picked:

import { openBlob } from '@qgustavor/las-reader/browser'

const reader = await openBlob(fileInput.files[0])

Finding points

import { pointsNear, matching } from '@qgustavor/las-reader'

for await (const point of pointsNear(
  reader,
  { x: 2230900, y: 252200, radius: 25 },
  { where: matching({ classification: [2, 9] }) }
)) {
  console.log(point.x, point.y, point.z, point.distance)
}

Queries reject points on the stored integers before decoding anything. On a file you will query more than once, build an index first so later queries skip most of it — see Working with large files.

Documentation

| Getting started | Opening files, reading points, what a point looks like | | --- | --- | | In the browser | Local files, Web Workers, HTTP | | In Node.js | Paths, file handles, streams | | Working with large files | Block indexes, caching, memory | | Finding points | Boxes, radii, attribute predicates, columns | | Coordinate systems | What the file declares, and reprojecting with proj4 | | Byte sources | The I/O interface and writing your own | | Compressed files | Reading .laz, chunk tables, sharing a WASM module | | API reference | Every export | | Migrating from 1.x | What changed and why |

Compressed files

LASzip (.laz) files open the same way .las files do:

const reader = await openFile('cloud.laz')

The openers read the header and pick the right reader, so callers do not have to know which they have. Decompression uses laz-perf in WebAssembly, loaded only when a compressed file is actually opened, so a bundle that reads only .las never pulls it in.

Chunks are decompressed as they are needed, so readPoint(4_000_000) costs one chunk rather than the whole file — see Compressed files.

License

Apache-2.0