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

chartjs-plugin-annotation-drag2

v1.5.3

Published

Annotations for Chart.js

Downloads

5

Readme

  1. everytime the mouse updates a function called updateListeners is called with 3 variables passed to it, these are passed everywhere throughout the lib:

    1. state: whether the annotation line has been clicked on or moved over
    2. args.event: what event has been detected
    3. options: chart options
  2. this does some stuff to check in your annotation options what event you have selected to detect

  3. then a function called handleEvent is called with the same options passed as updatelistener

  4. handleEvent sends you off to one of 2 functions depending on if its a mouseover or click: handleMoveEvents and handleClickEvents. handleMoveEvents is a little weirder but it all ends up going to what you see in step 4

  5. MORE WORK NEEDED: both handleMoveEvents and handleClickEvents pass a parameter to a function called getElements called options.interaction depending on the type of event (mouseover or mouseclick). These find whatever element the user is selecting and depending on this element the method to find that will be diffrent, for example 'mouseclick' does a 'getnearest' mode. Problem is I have no idea where this 'interaction' param is being generated.

  6. Now with what annotation the user has touched from getElements which executes the function found in there annotation options, and allows you to pass along the options of your chart to be changed.