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

html-js-confirm

v1.0.5

Published

A lightweight promisified reimplementation of the JavaScript confirm()

Readme

This package is a lightweight promisified reimplementation of the JavaScript confirm(). It uses a <dialog> element (with a polyfill) under the hood and not a lot else.

Instead of blocking code execution, this dialog returns a promise that resolves with a boolean of the answer.

Check out a demo!

Demo of package

But why?

Mostly because of cross-origin iframes and browser support. In Chrome 92+ confirm() cannot be triggered from an <iframe> when the frame is cross-origin. This implementation is HTML and JavaScript and will not be blocked.

Usage

Installation

npm install html-js-confirm

There are several ways to include the module:

  • import (ESM module)
  • require (CJS)
  • Include the dist/html-js-confirm.min.js in your HTML, which overwrites the JavaScript confirm() and replaces it with this implementation.
// direct import
import confirm from './node_modules/html-js-confirm/dist/html-js-confirm.esm.js';

// modern es modules with rollup/webpack bundlers and node via esm module
import confirm from 'html-js-confirm';

// traditional commonjs/node and browserify bundler
const confirm = require('html-js-confirm');

Don't forget to include the dist/html-js-confirm.css in your HTML for the <dialog> polyfill to work.

JS example

// using async await
async () => {
  if (await confirm('Are you sure you want to continue?')) {
    // we continue
  } else {
    // we cancel
  }
}

// using then
function() {
  return confirm('Are you sure you want to continue?')
    .then(continue => {
      if (continue) {
        // we continue
      } else {
        // we cancel
      }
    });
}

HTML example

<head>
  <link rel="stylesheet" type="text/css" href="dist/html-js-confirm.css" />
</head>
<body>
  <button type="button" id="good-time-button">
    Click for a good time!
  </button>

  <script type="text/javascript" src="dist/html-js-confirm.min.js"></script>
  <script>
    const button = document.getElementById('good-time-button');

    button.addEventListener('click', async () => {
      if (await confirm('Are you sure you want to have a good time?')) {
        console.log('🎉');
      } else {
        console.log('No party for you');
      }
    });
  </script>
</body>

Further reading

The <dialog> polyfill included with this package can be found here. If you are relying on the polyfill, you should read up on its limitations.