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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mapnik-pool

v0.1.3

Published

manage a pool of mapnik instances

Downloads

339

Readme

mapnik-pool

Build Status Coverage Status

mapnik-pool

If you want to use node-mapnik in an app with concurrency, you'll want to use a map pool. By design Mapnik Maps are not meant to be shared between threads because datasources hold state. This may change in the future but for now using a single map instance with async node-mapnik rendering functions may your app. Also using several map instances will give you a significant speedup. mapnik-pool manages a generic-pool of mapnik.Map instances so you don't have to.

install

npm install --save mapnik-pool

dependency structure

mapnik-pool is a peerDependency of node-mapnik: you bring your own Mapnik version, as long as its ~1.0.0.

example

var mapnik = require('mapnik'),
    mapnikPool = require('mapnik-pool')(mapnik),
    fs = require('fs');

var pool = mapnikPool.fromString(fs.readFileSync('mymap.xml', 'utf8'));

pool.acquire(function(err, map) {
    // pooled map
});

api

fromString(str, initOptions, mapOptions)

  • str: a Mapnik XML string
  • initOptions: options for initialization. Currently, size for map, bufferSize. Default { size: 256 }
  • mapOptions: options for the fromString method.