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

@developmentseed/epsg

v0.7.0

Published

The full EPSG projection database, compressed to 309kb for the web.

Readme

@developmentseed/epsg

The full EPSG projection database, compressed to 309kb for the web.

Some existing EPSG amalgamations exist, but all are uncompressed, incomplete, outdated, and/or not reproducible [^1] [^2] [^3] [^4]. This package uses the DecompressionStream API, now widely available in browsers, to bundle a gzip-compressed text file of WKT definitions for all 7352 defined EPSG projection codes.

[^1]: epsg includes only 3912 definitions, stores older, deprecated proj strings, and is uncompressed, coming to 500kb.

[^2]: epsg-index stores extra parsed information for each projection and is 7.7 MB.

[^3]: proj4-list includes only 5434 definitions, stores older, deprecated proj strings, and is 759KB of uncompressed strings.

[^4]: @esri/proj-codes ships a lot of redundant information, coming to nearly 15MB of JSON.

Usage

Currently, the only package entrypoint is @developmentseed/epsg/all, which loads a Map<number, string>, with all EPSG definitions in OGC WKT2 format.

import loadEPSG from "@developmentseed/epsg/all";
import proj4 from "proj4";

// Load the EPSG database
const epsg = await loadEPSG();

// Access WKT strings by EPSG code.
const wkt4326 = epsg.get(4326);
const wkt3857 = epsg.get(3857);

// Then use proj4.js as normal
const converter = proj4(wkt4326, wkt3857);
const inputPoint = [1, 52];
const outputPoint = converter.forward(inputPoint);

Generate new EPSG definitions

First, download the latest EPSG definitions in WKT format. Go to epsg.org/download-dataset.html, create an account or log in, then download the WKT File version.

Then, from this directory, run

python scripts/generate.py

Then the file src/all.csv.gz will be updated with the latest EPSG definitions.

Publishing

The build script in package.json will automatically include all.csv.gz in the published NPM package.

If you get an error like

cp: dist/all.csv.gz: No such file or directory

You may need to delete an errant tsconfig.build.tsbuildinfo and try again. I'm not sure why.