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

touch-pricker

v1.1.0

Published

Free Touch Pricker

Downloads

4

Readme

touch-pricker

Build Status

Free Touch Pricker

(WIP)

Currently supports a pricker for Stedman touches on various stages, based heavily on that created by Mark Davies.

Installation

Installation using npm

Install using npm or yarn:

# npm
npm install --save-dev touch-pricker

# yarn
yarn add --dev touch-pricker

Modify your page to include an element where the pricker will be mounted:

<div id="pricker"></div>

Then load using your preferred bundler and module syntax, either CommonJS:

const Pricker = require('touch-pricker');

const thePricker = Pricker.create('pricker'); // ID of mount element

... or using ES6 modules:

import Pricker from 'touch-pricker';

const thePricker = Pricker.create('pricker'); // ID of mount element

Installation from source

Download the source file of your choice from the dist directory of this repository:

  • development - touch-pricker.js
  • production - touch-pricker.min.js

Host the file locally and add to scripts:

<script type="text/css" src="touch-pricker.min.js"></script>

Modify your page to include an element where the pricker will be mounted:

<div id="pricker"></div>

... and then load it:

<script type="text/javascript">
  window.onload = function () {
    var thePricker = Pricker.create('pricker'); // ID of mount element
  };
</script>

See examples/mbd.html for a full example.

Configuration

The Pricker.create() call has the following signature:

Pricker.create(id: string, config: any): Pricker.Pricker.Abstract;

This currently supports the following configuration option:

iframe

{
  iframe: true // default
}

Controls whether to create the pricker within an <iframe> element in order to isolate it from the parent page. This prevents scripts or styles leaking between the pricker and its host, but makes debugging more difficult.

Development

Prerequisites

  1. Install nvm (or manually install a node version compatible with that defined in nvmrc).

  2. Install yarn.

Quickstart: build and run tests

nvm install
yarn install
bin/gulp

Available gulp targets

  • build - builds source code
  • build-tests - builds testcases (depends on build)
  • docs - builds TypeDoc documentation
  • test - runs unit tests under PhantomJS (default)
  • test-browsers - runs unit tests under various browsers (see karma.conf.js)
  • watch - rebuild whenever changes are made

Yarn / npm scripts

  • build - as above
  • lint - calls tslint in isolation
  • test - as above
  • watch - as above

To test in a browser window

Build tests (bin/gulp build-tests) then load up /jasmine.html.