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

dwg2geo

v0.2.3

Published

Convert engineering DWG drawings to GeoJSON in the browser or Node (WebAssembly)

Readme

dwg2geo (npm)

Convert engineering DWG drawings to GeoJSON entirely in the browser or Node — the pure-Rust dwg2geo converter compiled to WebAssembly. No native dependencies, no server.

npm install dwg2geo

Browser (or any runtime where fetch resolves module-relative URLs):

import init, { convert } from 'dwg2geo';

await init(); // fetches and instantiates the wasm module

const bytes = new Uint8Array(await file.arrayBuffer()); // a .dwg file
const result = convert(bytes, /* polygonize_closed */ false, /* curve_tolerance */ undefined);

const fc = JSON.parse(result.geojson); // GeoJSON FeatureCollection (local drawing coordinates)
console.log(result.feature_count, result.converted, result.skipped, result.warnings);

Node (no fetch for file: URLs — pass the wasm bytes explicitly):

import { readFile } from 'node:fs/promises';
import init, { convert } from 'dwg2geo';

const wasm = await readFile(new URL('./node_modules/dwg2geo/dwg2geo_wasm_bg.wasm', import.meta.url));
await init({ module_or_path: wasm });

const result = convert(new Uint8Array(await readFile('drawing.dwg')), false, undefined);

The result mirrors dwg2geo's EmbedResult:

| field | meaning | |---|---| | geojson | FeatureCollection string in the drawing's local coordinates | | feature_count, model_space_entities | totals | | converted / skipped / failed | per-entity-type outcome counts with reasons | | warnings | conversion warnings | | bbox | [minx, miny, maxx, maxy] or null | | source_sha256 | hash of the input bytes (audit trail) |

Features carry resolved CAD style metadata (layer, color_rgb, color_index, linetype, lineweight_mm, text properties…). Coordinates are local — georeference them yourself (e.g. proj4js) with the drawing's known CRS; dwg2geo never guesses one.

Deterministic: the same bytes always produce byte-identical GeoJSON on a given platform (across platforms — native vs WebAssembly — a few floating-point values may differ in the last digit).

Built with wasm-pack --target web. See a full working app at dwg2geo-app (live demo).

License: MIT.