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

svg-projections

v1.0.7

Published

Facilities to use svg transforms to project data, rather than d3 scales directly

Downloads

8

Readme

What is it?

An SVG projection means moving elements by adjusting the containing element's transform, rather than updating each item's coordianates as the space is scrolled and panned.

In practice, for many visualisations this is orders of magnitude faster because much fewer DOM changes are required for common use cases such as scrolling.

For d3 projects.

const svgProjection = require('svg-projections')

let x = d3.scales.linear()
let y = d3.scales.time()

let area = d3.select('#something')

/**
* needsStroke
* -----------
*
* Set to true if the area being projected needs to maintain proportionality of the thickness of
* stroke. In browsers that support svg non-scaling-stroke property the performance will be better
* than those which do not. For browsers that do not, a slower callback is used.
*
* If using stroke inside a projection, it is assumed that vector-effect:non-scaling-stroke
* is in your svg css
*
* preserveAspect
* --------------
*
* Set to true if the aspect of the area being projected needs to be preseved. For example,
* if you are using <circle> elements and would like them to stay circular. For general paths
* this is not required.
*/

let projection = svgProjection({x, y}, d3.select('#something'), {needsStroke: false, preserveAspect:false})

area.selectAll('.dataPoint')
    .data(myData)
    .enter()
    .append('path')

    // when positioning elements, now use projection.x and projection.y
    // instead of x and y directly
    .attr('x1', d => projection.x(d.value1) )
    .attr('x2', d => projection.x(d.value2) )
    .attr('y1', d => projection.y(d.time1) )
    .attr('y2', d => projection.y(d.time2) )

// whenever scales change, update the transform on the container:
projection.updateSpace()