# pretty-js

> Beautify / pretty print JavaScript and JSON

Latest version **0.2.2** (published 2021-05-19) · MIT license · 0 weekly downloads

## Install

```sh
npm install pretty-js
pnpm add pretty-js
yarn add pretty-js
bun add pretty-js
```

Provides the command `pretty-js`.

## Health

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

Positive: no vulnerabilities.

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

Negative: abandoned.

## Facts

| | |
|---|---|
| Version | 0.2.2 |
| Published | 2021-05-19 |
| First published | 2014-10-07 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 4 |
| Unpacked size | 101.9 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 22 |
| Author | Tyler Akins |
| Maintainers | fidian |
| Keywords | beautify, prettyprint, pretty, print, javascript, js |

## Links

- npm: https://www.npmjs.com/package/pretty-js
- Repository: https://github.com/tests-always-included/pretty-js
- Issues: https://github.com/tests-always-included/pretty-js/issues
- npm.io page: https://npm.io/package/pretty-js

## Dependencies (4)

- [complexion](https://npm.io/package/complexion.md) ^0.2.2
- [complexion-js](https://npm.io/package/complexion-js.md) ^0.2.2
- [option-parser](https://npm.io/package/option-parser.md) ^1.0.0
- [process-files](https://npm.io/package/process-files.md) ^1.0.0

## Alternatives

- [@mapbox/jsonlint-lines-primitives](https://npm.io/package/@mapbox/jsonlint-lines-primitives.md) — 5.3M weekly downloads
- [reftools](https://npm.io/package/reftools.md) — 3.5M weekly downloads
- [@hey-api/openapi-ts](https://npm.io/package/@hey-api/openapi-ts.md) — 3.5M weekly downloads
- [@mapbox/geojson-rewind](https://npm.io/package/@mapbox/geojson-rewind.md) — 2.4M weekly downloads
- [turbo-stream](https://npm.io/package/turbo-stream.md) — 1.7M weekly downloads

## Recent versions

- 0.2.2 (latest) — 2021-05-19
- 0.2.1 — 2019-11-20
- 0.2.0 — 2017-07-25
- 0.1.8 — 2015-01-13
- 0.1.7 — 2014-11-21
- 0.1.6 — 2014-11-07
- 0.1.5 — 2014-10-13
- 0.1.4 — 2014-10-12
- 0.1.3 — 2014-10-08
- 0.1.2 — 2014-10-07
- 0.1.1 — 2014-10-07

## README

PrettyJS
========

Beautify / pretty print JavaScript and JSON.  Turn really ugly and poorly indented files into masterpieces.

[![npm version][npm-badge]][npm-link]
[![Build Status][travis-badge]][travis-link]
[![Dependencies][dependencies-badge]][dependencies-link]
[![Dev Dependencies][devdependencies-badge]][devdependencies-link]


Requirements
------------

You must have an ECMAScript 5 environment.  If you're in a browser or otherwise don't have convenient things like `Array.prototype.forEach` then you can use [es5-shim] to patch in the necessary functions.

This also relies on [Complexion] and [ComplexionJS].  If you plan on using this in a web browser, I strongly suggest you look into [Browserify] or a similar technique to bundle up JavaScript.


Installation
------------

When you want to run `pretty-js` from the command line, use `npm` to install the script globally.

    npm install -g pretty-js

If you'd rather call the library directly, then list "pretty-js" as a dependency in your `package.json` file and let `npm` install it locally.  You can do it easily with `npm`.

    npm install --save-dev pretty-js


Running via Command Line
------------------------

Did you install this script globally?  (`npm install -g pretty-js`)  If so, you now have the boundless power of the JavaScript pretty printer in a convenient command-line interface.

    pretty-js [options] [filename ...]

Here are a few typical ways to run the pretty printer.

    # Beautify ugly.js
    pretty-js ugly.js > pretty.js

    # Format JSON
    pretty-js -j ugly.json > pretty.json

    # Use Windows linefeeds and jslint-compatible rules
    # Overwrites original file with formatted content
    pretty-js --newline CRLF --jslint --in-place source-code.js

    # Rewrite all JavaScript files and display the name of the
    # file being changed
    pretty-js -i -v *.js

There's a lot of options and you can control all of the aspects of the pretty printer.  Use `pretty-js --help` for a lot of information.  Reading from stdin is an option as well, thanks to [processFiles].  All of the following read from stdin and write to stdout.

    cat ugly.js | pretty-js > pretty.js

    cat ugly.js | pretty-js - > pretty.js

    # The "in-place" editing of stdin just writes to stdout
    cat ugly.js | pretty-js -i > pretty.js


Using the API
-------------

I find that code examples are very illustrative.

```js
var code, options, prettyJs;

// Load the library
prettyJs = require('pretty-js');

// Let's format some code quickly with the defaults
code = '// some JavaScript code goes in here';
console.log(prettyJs(code));  // Displays formatted code

// Format code and specify a couple options
options = {
    indent: "\t",  // Switch to tabs for indentation
    newline: "\r\n"  // Windows-style newlines
};
console.log(prettyJs(code, options));
```


Options
-------

All of these options are also available when using the command-line interface.  When there is a difference in the default value, that is explained for each option along with the reasoning behind the difference.


### bom (boolean or null)

Always add, remove, or just preserve the BOM (byte order mark) in a file.  The BOM can cause problems plus JavaScript and JSON files are expected to typically be in UTF-8.

* `true`: Always add a BOM to the file
* `false`: Always remove a BOM from the file
* `null`: Preserve a BOM if one exists

Defaults to false to help remove problems.


### commentSpace (string)

Spaces to the left of single-line comments.

```js
someFunction();  // single-line comment
```

Defaults to `"  "` (two spaces)


### convertStrings ("double", "single", false/null)

Strings can be `'single quoted'` or `"double quoted"`.  For consistency, the pretty printer will change (and properly re-escape) strings to match your preferred style.

Defaults to double so it works better with JSON.


### elseNewline (boolean)

When enabled, put `else` and `catch` on a new line.  When disabled, those keywords will be on the same line as the previous closing brace.

Defaults to false.


### indent (string)

What to use for a single indentation level.

The eternal "spaces vs. tabs" debate comes up a lot.

Defaults to `"    "` (four spaces).


### jslint (boolean)

When truthy this uses jslint-compatible rules.  For instance, this forces `quoteProperties` to be false.  There's some other changes regarding switch blocks and punctuation as well.

Defaults to false.


### newline (string)

This is the string to use for newlines.

* "\n" is for Mac, Unix and Linux
* "\r\n" is for Windows
* "\r" is the old Mac style

Defaults to `"\n"` (Mac/Unix/Linux style).


### noSpaceAfterIf (boolean)

Enabling this option removes the space that would appear in `if (`.

Defaults to false.


### noSpaceAfterFor (boolean)

Enabling this option removes the space that would appear in `for (`.

Defaults to false.


### noSpaceAfterFunction (boolean)

Enabling this option removes the space that would appear in `function (`.  Please note that this is only applied for anonymous functions, not named functions.

Defaults to false.


### noSpaceAfterSwitch (boolean)

Enabling this option removes the space that would appear in `switch (`.

Defaults to false.


### noSpaceWithIncDec (boolean)

Enable this option to remove the space between an identifier and the ++ or --.

Defaults to false.


### quoteProperties (boolean or null)

Wrap object properties in quotes or remove them.

* `true`: Always add quotes around properties
* `false`: Always remove quotes around properties when syntactically possible
* `null`: Keep quoted properties quoted and unquoted properties unquoted

Defaults to false.


### trailingNewline (boolean)

Adds or removes newline at end of file.

* `true`: Always add newline to end of file
* `false`: Always remove newline from end of file

Defaults to false.


Development
-----------

If you want to work on this library, you need to check out the repository and run `npm install` to get the dependencies.

Tests are *always* included.  Make sure tests cover your changes.  To run the current tests, just use `npm test` or `grunt test` (they will run the same test suite).


License
-------

This software is licensed under an [MIT license with an additional non-advertising clause](LICENSE.md).


[Browserify]: http://browserify.org/
[Complexion]: https://github.com/tests-always-included/complexion
[ComplexionJS]: https://github.com/tests-always-included/complexion-js
[dependencies-badge]: https://img.shields.io/david/tests-always-included/pretty-js.svg
[dependencies-link]: https://david-dm.org/tests-always-included/pretty-js
[devdependencies-badge]: https://img.shields.io/david/dev/tests-always-included/pretty-js.svg
[devdependencies-link]: https://david-dm.org/tests-always-included/pretty-js#info=devDependencies
[es5-shim]: https://github.com/es-shims/es5-shim
[npm-badge]: https://img.shields.io/npm/v/pretty-js.svg
[npm-link]: https://npmjs.org/package/pretty-js
[processFiles]: https://github.com/tests-always-included/process-files
[travis-badge]: https://img.shields.io/travis/tests-always-included/pretty-js/master.svg
[travis-link]: http://travis-ci.org/tests-always-included/pretty-js

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