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

@getchange/getchange.io-modules

v1.17.0

Published

[npm]: https://img.shields.io/npm/v/@getchange/getchange.io-modules [npm-url]: https://www.npmjs.com/package/@getchange/getchange.io-modules

Downloads

74

Readme

getchange.io-modules

npm

This repository contains modules used by the getchange.io website.

Why?

  1. Development is much easier here than in Webflow.
  2. Custom JS needs to be linkable from an HTML embed tag in Webflow. Bundling a module and publishing it to NPM allows us to easily link to it from the Webflow embed tag.
  3. Some modules are also used in our dashboard or other places. Having one central repository makes it easy to update all of them at once.

Get started

# Start the dev server
npm run dev
# In another terminal, start the build process
npm run build:dropin:watch

Visit http://localhost:8000/dev/change-demo.html

(For another module, visit a different page in dev/).

All the dev html pages should use the "dropin" version of the build.

Build for production

There are two ways to build a module for production: "dropin" and "importable".

Dropin

npm run build:dropin

Dropin modules are built to be included in a Webflow project. They are built to a single file, build-dropin/bundled-*.js, which can be included in a Webflow embed tag like this:

<script type="module" src="https://unpkg.com/@getchange/[email protected]/build-dropin/bundled-change-demo.js"></script>

Importable

npm run build:importable

Importable modules are built to be imported in a TypeScript or JavaScript project. They are built to javascript files and TS declaration files in the build-importable/* folder. You can import them like this:

# First, install the package in your project
npm i @getchange/getchange.io-modules
// Then, you can import the module like this:
import '@getchange/getchange.io-modules/build-importable/change-demo';