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

use-strict

v1.0.1

Published

Makes all modules in Node get loaded in strict mode.

Downloads

234,488

Readme

use-strict

Makes all modules in Node get loaded in strict mode.

Usage

require('use-strict')
// That's it, now everything is strict forever.
// in other words: FTFY, YOU'RE WELCOME.

Downside

Strict mode in JavaScript is virtually always a great thing. It prevents accidental global leakage, turns silent mistakes into errors, and removes with and arguments.callee and their sordid complexities. It's mostly a Good Thing.

Unfortunately, it also removes octal literals, which is kind of a bummer. You can pass octal strings to Node's functions that deal with file modes, and they'll do the right thing, so it's not completely horrible.

The implementation works by patching Node's internal module.wrapper array, and then freezing it, so that further modifications are not possible.

This means that error printouts that occur on the first line of a node module will be off by a few characters, since Node does a bit of math to account for its wrapper script, which will now be off by 13 characters. This is probably not a big problem, and not really worth working around.

Also, this means that the current module will not be affected. You should still "use strict" in the module that does require('use-strict'). This module applies strictness to all future modules loaded by your program.

Note You can also run node --use_strict and get the same effect without any of the caveats.