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

axes

v0.0.0

Published

An alternative implementation of d3's quantitative scales

Downloads

17

Readme

axes experimental

An alternative to d3's quantitative scales that handles multiple axes a little more conveniently.

I've found that in larger d3 projects I tend to create a few duplicate scales across multiple charts, when really they'd be easier to manage/update them as a group: being passed around into each chart as required, responding to updates being made in other parts of the code.

Installation

$ npm install --save axes

Example

var linedata = require('./linedata.json')
var bardata = require('./bardata.json')
var d3 = require('d3')

var axes = require('axes')()
  .def('barX')
    .domain([0, bardata.length])
  .def('barY')
    .domain([0, d3.max(bardata)])
  .def('lineX')
    .domain([0, linedata.length])
  .def('lineY')
    .domain([0, d3.max(linedata)])
  .root()

// Alias your scales so they play nice
// with the code you're giving it.
axes.barX(2) // 0.5
axes.alias({ x: 'barX' }).x(2) // 0.5

// Throw them into your charts
require('./barchart')({
  axes: axes.alias({
      x: 'barX'
    , y: 'barY'
  })
})
require('./linechart')({
  axes: axes.alias({
      x: 'lineX'
    , x: 'lineY'
  })
})

// Use `axis.map` for alternative value
// mappings.
var angle = axes.barX.map(function(n) {
  return n.value * Math.PI * 2
})

angle({ value: 2 }) // 3.14159265...

API

axis = require('axes').def()

Returns an anonymous scale, which is very similar to d3.scale.linear, but a more limited API.

axis.domain([domain])

Takes an 2-element array defining the minimum and maximum input values for the scale.

axis.range([range])

Takes an 2-element array defining the minimum and maximum output values for the scale.

axis()

Returns a number between range[0] and range[1] depending on how far it is between domain[0] and domain[1].

axis.on('update', handler(key))

The "update" event is called on handler every time the axis' range or domain properties are updated.

axis.copy()

Creates a copy of the axis, so that you can change its domain and range values without altering the original one.

scale = axis.map([map])

Returns a scale that maps its output according to map. The initial value will be scaled based on axis's output. You can update these values in the original scale and the scale's range will update accordingly too.

scale()

The returned scale essentially boils down to:

axis().map(mapper)(n) === mapper(axis(n))

axes = require('axes')()

Returns a new group of axes.

member = axes.def(name)

Returns a named scale, attached to this group.

member.root()

Returns the group of axes.

member[fork|alias|def]()

The fork, alias and def methods on each group member will be called from the group, to make for easier chaining.

axes.fork(new, old)

Creates a copy of the group's member called old, called new.

axes.alias(map)

Returns a copy of the group, while preserving the original references to each member. map is an object: the keys determine the new name, and the values determine the old one.

var axes = require('axes')()
  .def('oldX')
  .range([0, 100])

var aliased = axes.alias({
  oldX: 'newX'
})

axes.oldX(0.5)    // 50
aliased.newX(0.5) // 50
aliased.oldX(0.5) // Object #<Object> has no method 'oldX'

axes.copy()

Copies the whole group, copying each member reference as well so you can make can changes to this copy without having to worry about altering the other scales.