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

signupsio.js

v0.3.1

Published

DEPRECATED - Client-side Form Tracking for Signups.io

Downloads

3

Readme

DEPRECATION WARNING

Signups.io has moved to Formster.io, so this package no longer functions. Use the formster.js package instead.

signupsio.js - the Signups.io Client-side Library

Signups.io is a service to let you easily create and track sign up forms on static web pages. For more information and examples, visit Signups.io.

Installation

CDN (recommended)

Signups.io maintains a CDN for the signupsio.js Library (built as a standalone). The format for requests to the CDN is: protocol://cdn.signups.io/{version}/{script}

Simply drop a script tag in, and you're ready to go:

    <script src="//cdn.signups.io/v0.3.0/signupsio.min.js"></script>

Standalone

The signupsio.js library is built using Browserify. Standalone libraries are available in [build/](/build), and are exposed to the window object as Signupsio if no other module system is detected. Browserify uses UMD to expose standalone modules.

Browserify

To include the client-side library in your own Browserify build, just install the signupsio.js package through npm:

    $ npm install signupsio.js

Usage

Auto Tracking

signupsio.js automatically scans the page for <form>s with a className of signupsio on DOMReady. Upon finding them, it instantiates the API and starts tracking. For the majority of cases, this automatic tracking is sufficient. To trigger auto tracking at a later time, call the auto method of the Signupsio object:

    function callMeLater() {
      Signupsio.auto();
    }

Signupsio.js keeps track of which forms it is tracking, so calling auto multiple times will not result in a duplication of data.

Manual Tracking

In some cases, more control over the form tracking process might be desirable.

Instantiation

Signupsio is a constructor for the API which takes the API key as its only parameter:

    var signupsio = new Signupsio('YOUR_API_KEY');

Track Form

To track a form (including form clicks and submissions), pass the DOM element to the trackForm method:

    signupsio.trackForm($("#my-form-id").get(0));

Page Visit

To track a visit to a page, use the visit method with a page name as the only paramter:

    signupsio.visit("lead-form");

Underlying API Library

The guts of signupsio.js, most users will never need to touch the underlying library. However, it is exposed on the Signupsio object as Signupsio.Api. Any changes made to the Api object will be used in all future instances of Signupsio.