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

atom-popup

v0.1.0

Published

Small popup based on atomic

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

uppercoduppercod

Keywords

Readme

atom-popup

This is a small skeleton to create distributable components based on Atomico.

The component is packaged thanks to rollup.config.js, you can execute the commands

# alias rollup -c -w
npm run watch
# alias rollup -c
npm run build

package.json

The output files of the package are defined within package.json, this is thanks to rollup-prepare.

 "name": "atom-popup",
 "main": "dist/atom-popup.js",
 "umd:main": "dist/atom-popup.umd.js",
 "iife": "dist/atom-popup.iife.js",
 "module": "dist/atom-popup.m.js",
 "source": "src/index.js",

| Property | Description | |-----------|-------------| | name | Necessary for the exit of the files type umd:*| | main | Allows to generate a component in output format CJS | | umd:main | Allows to generate a component in output format UMD | | iife | Allows to generate a component in output format IIFE | | module | Allows to generate a component in output format ES | | source | component source file |

Component installation

<body>
    <atom-popup></atom-popup>
    <!-- polyfill --> 
    <script src="https://unpkg.com/@webcomponents/[email protected]/webcomponents-loader.js"></script>
    <!-- size 1.7kB -->
    <script src="https://unpkg.com/[email protected]/dist/atomico.umd.js"></script>
    <!-- size 1.4kB -->
    <script src="https://unpkg.com/[email protected]/dist/atom-popup.umd.js"></script>
</body>

The scripts can also load from the <head>.