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 🙏

© 2026 – Pkg Stats / Ryan Hefner

custom-windy-picker

v1.0.17

Published

Custom Windy Picker, for windy-plugins

Readme

custom-windy-picker

This is a custom windy picker made for plugins.

It includes a drag listener and allows you to add content to the picker.

How to use it:

To installed it and add to package.json:

npm install custom-windy-picker

In your plugin.svelte, or any other modules where you need it:

import { getPickerMarker } from 'custom-windy-picker';
const marker = getPickerMarker();

getPickerMarker creates a leaflet marker, if it has not yet been made, or gets it from W.plugins['custom-picker-for-windy-plugins']

marker then has the following methods:

  • openMarker(latLon)
  • removeMarker()
  • getParams() : returns latLon with source: 'custom-picker'. If the picker is not open (!marker.isOpen), will return null
  • destroyMarker() : Called internally when custom-picker is no longer used. Detected with checkIfMustClose()
  • onDrag(cbf,intv)
  • offDrag(cbf)
  • onOpen(cbf)
  • offOpen(cbf)
  • onClose(cbf)
  • offClose(cbf)
  • fillLeftDiv(string | html div element, pickerBckgCol = false ) : If pickerBckgCol == true the right div will be grey, otherwise transparent.
  • fillRightDiv(string | html) : Same as left, only pickerBckgColor not needed.
  • addLeftPlugin(plugin-name) : A list of plugin names is maintained that uses the left side of the picker. addLeftPlugin pushes the plugin name to the list. This plugin then has priority to when using fillLeftDiv
  • remLeftPlugin(plugin-name) : The plugin_name is removed from the list, the next on the list now gets priority
  • getLeftPlugin(): returns plugin-name
  • same for RightPlugin

Notes:

Opening, moving or closing the plugin, will also trigger the internal windy eventer, thus will trigger picker.on('opened', cbf) and 'closed' and 'moved'.

If the picker.less is changed, run less2css.js, to write the new src/pickerCss.js.

You are welcome to use it, but if you change the code, DO NOT attach it to W.plugins['custom-picker-for-windy-plugins'], else you will mess up my plugins.

If you use it in an embedded plugin, there are some finicky things to be aware of, see my windy-plugin-demo.