# use-strict

> Makes all modules in Node get loaded in strict mode.

Latest version **1.0.1** (published 2015-05-20) · ISC license · 0 weekly downloads

## Install

```sh
npm install use-strict
pnpm add use-strict
yarn add use-strict
bun add use-strict
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.1 |
| Published | 2015-05-20 |
| First published | 2013-04-29 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 37 |
| Author | Isaac Z. Schlueter |
| Maintainers | isaacs |
| Keywords | use strict, strict mode |

## Links

- npm: https://www.npmjs.com/package/use-strict
- Repository: https://github.com/isaacs/use-strict
- Homepage: https://github.com/isaacs/use-strict#readme
- Issues: https://github.com/isaacs/use-strict/issues
- npm.io page: https://npm.io/package/use-strict

## Recent versions

- 1.0.1 (latest) — 2015-05-20
- 1.0.0 — 2013-04-29

## README

# use-strict

Makes all modules in Node get loaded in strict mode.

## Usage

```javascript
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.

---
_Source: https://npm.io/package/use-strict · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._