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

wscript-avoider

v4.0.1

Published

DEPRECATED: Validation code to avoid running under Windows Script Host (specific to older Windows machines)

Downloads

109

Readme

DEPRECATED!

After a thorough analysis, it was discovered that the design of this module is flowed, the detection of WSH cannot be performed later in the code, since WSH will not run the advanced ES6 classes.

The correct sequence is to run the check right at the beginning of the script.

Example of a CLI launcher which refuses to run on WSH:

#!/usr/bin/env node
// Mandatory shebang must point to `node` and this file must be executable.

; (function () { // wrapper in case we're in module_context mode
  /* global WScript */
  if (typeof WScript !== 'undefined') {
    // Windows only: the script was caught by WSH, not node.
    WScript.echo('Run this with node, not the Windows Script Host\n\n')
    WScript.quit(1)
  }

  // --------------------------------------------------------------------------

  const Main = require('../index.js').Main

  // `start()` is async (a promise), thus `.then()` is needed
  // to wait for it to complete.
  Main.start().then(
    (code) => process.exit(code)
  )
})()