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

betterknown

v1.2.0

Published

_betterknown development is supported by ๐ŸŒŽ [placemark.io](https://www.placemark.io/)_

Readme

betterknown

betterknown development is supported by ๐ŸŒŽ placemark.io

I wrote wellknown, a WKT parser and stringifier, eons ago. It's still sort of popular but nobody maintained it after I left Mapbox.

There's wkx, which is stricter and honestly has a better parser, plus supports WKB, but it's also abandoned and has some drawbacks - no TypeScript, somewhat idiosyncratic code, and the bundle size is larger than it needs to be because it brings in browserify shims.

This project aims to be the combination of the two projects. Lightweight like wellknown, strict and correct like wkx, plus with the 2022 energy of supporting TypeScript from day one.

  • 100% TypeScript
  • No dependencies - tiny bundle
  • Parse WKT to GeoJSON, stringify GeoJSON to WKT
  • Optional reprojection of EWKT to GeoJSON's required WGS84 coordinate system
  • Support for GeoSPARQL-flavored WKT

๐Ÿ“• Documentation

Example

import { wktToGeoJSON, geoJSONToWkt } from "betterknown";
import proj4 from "proj4";

// Converting & reprojecting an EWKT string
wktToGeoJSON(`SRID=3857;POINT(-400004.3 60000.1)`, {
  proj: proj4,
});

// Converting GeoJSON to WKT
geoJSONToWkt({
  type: 'Point',
  coordinates: [1, 2]
});

GeoSPARQL-flavored WKT

This specification of WKT specifies Literal Axis Order, which diverges from WKT and EWKT.

For example the input

<http://www.opengis.net/def/crs/EPSG/0/4326> Point(33.95 -83.38)

Produces this GeoJSON, with flipped coordinate order.

{
  "coordinates": [-83.38, 33.95],
  "type": "Point",
}

The behavior of Betterknown in this situation is:

  • If the IRI is exactly http://www.opengis.net/def/crs/EPSG/0/4326, then we flip coordinates.
  • If it is provided and not exactly that string, then we call the proj method, and you're in charge of reprojection and flipping coordinates: the proj method will receive the IRI string. Note that proj4 does not support the IRI-style projection URLs, so you'll have to include custom code here. An example of using proj4 with these URLs is listed below.