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

sample-uit-agr-app

v1.0.2

Published

sample uit aggregation functions app

Downloads

3

Readme

sample-uit-agr-app

This shows how to distribute an ES6 library using Babel and rollup.

  • package.json#module points to the raw ES6 code for modern browser consumption
  • package.json#main points to legacy browser/node support and CommonJS modules.

Under the hood, it uses Babel and babel-runtime for legacy browser/Node.js support. babel-runtime (actually the transform-runtime plugin) polyfills only what the library uses and does so in a way that doesn't conflict with other versions of Babel. This is perfect for libraries.

We use rollup only to create the UMD bundle for JSFiddle consumption.

Building

npm run build
// then publish to npm...

Installation

npm install sample-uit-agr-app // from an app

Consumption

// Web, webpack consumption, modern browsers only
import foo from "sample-uit-agr-app";
// Web, webpack consumption, legacy browser support
import foo from "sample-uit-agr-app/dist/legacy/index";
// Node.js
const foo = require("sample-uit-agr-app");

JSFiddle support: dist/legacy-umd/index.js is a UMD bundle that can be put behind a CDN and loaded via a <script> tag. For example, here it is via jsdeliver.com, and here it is in a fiddle.