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

native-dns-cache

v0.0.2

Published

DNS Caching Library

Downloads

61,641

Readme

Cache

If you perform a query on an A or AAAA type and it doesn't exist, the cache will attempt to lookup a CNAME and then resolve that.

The constructor takes an optional object with the following properties:

  • store -- implements the cache store model (optional, default MemoryStore)

Methods:

  • lookup(question, cb) -- for a given question check the cache store for existence
  • store(packet) -- iterates over the resource records in a packet and sends them to the cache store
  • purge() -- clears the cache store of all entries

MemoryStore / Cache store model

MemoryStore(opts) -- An in memory store based on a js object

Methods:

  • get(domain, key, cb)
  • domain is the holder under which keys will be applied, key is the subdomain that is being queried for. If you get('example.com', 'www', cb) you are really asking for www.example.com.
  • cb(err, results) -- results is an object of types and array of answers
  • { 1: [{address: '127.0.0.1', ttl: 300, type: 1, class: 1}] }
  • set(domain, key, data, cb)
  • domain is the parent under which this key is stored. key is the subdomain we are storing, data is an object of types with an array of answers.
  • set('example.com', 'www', {1: [{class:1, type:1, ttl:300, address:'127.0.0.1'}]}, cb)
  • cb(err, data) -- cb merely returns the data that was passed.
  • delete(domain[, key[, type]], cb) -- delete all from a domain, a domain and key, or a domain a key and a type.

Lookup

Is a mechanism that given a store performs the common resolution pattern.

Given example.com previous added to a store:

  • www.example.com CNAME foo.bar.example.com.
  • *.example.com A 127.0.0.1

A Lookup(store, 'example.com', {name:'www.example.com', type:1}, cb) will resolve www to the CNAME and then search for foo.bar.example.com which will return no results, and then search for *.bar.example.com which will also return no results, and ultimately searches for *.example.com which will return the desired record.

Callback will be called with (err, results) where results is an array suitable for use in Packet.answer