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

node-native-dialog

v2.0.0

Published

Display a native dialog from your Node.js app.

Downloads

14

Readme

npm version License: MIT

node-native-dialog

PRs for macOS/Linux welcome! (see Contributing)

Display a native dialog from your Node.js app. The difference to e.g. dialog is that this does not spawn a separate process for showing the dialog.

Because of this, it also lends itself better to be used in apps that make use of packaging with tools like pkg.

Windows 11 example

node-dialog Windows 11 Screenshot

Windows 7 example

node-dialog Windows 7 Screenshot

Usage

const dialog = require('node-native-dialog');

dialog.showSync({
	msg: 'Execution pauses here until user dismisses dialog.',

	// Same options as below
});

dialog.show({
	msg: 'Wow, native GUI feedback...',

	// Everything below is optional
	timeout: 3, // Seconds - floating point numbers are rounded
	title: 'node-dialog',
	icon: dialog.INFO,
	buttons: dialog.YES_NO_CANCEL,
	defaultButton: dialog.RIGHT,
})
.then((result) => {
	if(result === dialog.RESULT_TIMEOUT) {
		console.log('User did not respond in time.');
	}
	else if(result === dialog.RESULT_CANCEL) {
		console.log('User chose default button.');
	}
	else {
		console.log('Some other choice.');
	}
});

Notes

Windows

In order for the dialog to not appear blurry on displays that don't use 100% scale, you can enable the following compatibility setting for node.exe:

node compatibility setting

The constants listed below are in accordance with the following but the they have been renamed to conform better with what one is used to from the web and to be more neutral (future multi-platform compatibility): https://technet.microsoft.com/en-us/library/ee156593.aspx

macOS

No implementation yet.

Linux

No implementation yet.

Constants

Icons

ERROR
QUESTION
WARNING
INFO

Buttons

OK
OK_CANCEL
ABORT_RETRY_IGNORE
YES_NO_CANCEL
YES_NO
RETRY_CANCEL

Default Buttons

LEFT
MIDDLE
RIGHT

Results

RESULT_TIMEOUT

RESULT_OK
RESULT_CANCEL
RESULT_ABORT
RESULT_RETRY
RESULT_IGNORE
RESULT_YES
RESULT_NO

Contributing

It's fine if you can't implement all the same icon or button types but it should use a native implementation like winax does with wrapping ActiveX objects.