Package Exports
- prettier-standard
- prettier-standard/src/cli
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (prettier-standard) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
(✿◠‿◠) prettier-standard

prettier and standard brought together
While standard is a linter, prettier-standard is a formatter. You don't have to fix any warnings anymore 😌
Warning: Most recent version of prettier-standard is compatible with eslint >= 5 and node >= 8. If you're looking for support for older versions of eslint or node please npm install --save prettier-standard@8
Installation
yarn add --dev prettier-standardIf you're using the
npm:npm install --save-dev prettier-standard.
You can also install globally with
npm install -g prettier-standard
Usage
Prettier and standard brought together!
Usage
$ prettier-standard [<glob>]
Options
--since Format files changed since given revision
--changed Format only changed or added lines
--check Do not format, just check formatting
--parser Force parser to use (default: babel)
Examples
$ prettier-standard '**/*.{js,css}'
$ prettier-standard --since HEAD
$ prettier-standard --changed
$ echo 'const {foo} = "bar";' | prettier-standard
$ echo '.foo { color: "red"; }' | prettier-standard --parser cssWarning: --changed flag should be considered experimental as prettier has issues with range formatting:
Usage
Typically you'll use this in your npm scripts (or package scripts):
{
"scripts": {
"format": "prettier-standard '**/*'"
}
}We also encourage to use husky and lint-staged. You can configure it as follows:
{
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
},
"lint-staged": {
"linters": {
"**/*": ["prettier-standard", "git add"]
}
}
}NOTE: Unlike prettier this package simplifies your workflow by making --write flag a default, and allowing for passing code to stdin without additional --stdin flag.
Vim
It's probably best to use ale plugin. It supports multiple fixers, including prettier-standard:
Plug 'w0rp/ale'
let g:ale_fixers = {'javascript': ['prettier_standard']}
let g:ale_linters = {'javascript': ['']}
let g:ale_fix_on_save = 1Sublime Text 3
It's possible to use 'prettier-standard' with Sublime Text 3.
- Install 'prettier-standard' globally according to the installation instructions above.
- Find the location of your installed executable file. On a unix based system (like MacOS):
$ which prettier-standard- Copy the location. (e.g.
/usr/local/bin/prettier-standard) - Install SublimeJsPrettier according to their installation instructions.
- Open SublimeJsPrettier's default settings in Sublime and copy the line:
"prettier_cli_path": "" - Open SublimeJsPrettier's user settings in Sublime and add the line with the correct location of the 'prettier-standard' executable.
{
"prettier_cli_path": "/usr/local/bin/prettier-standard"
}You can now use 'prettier-standard' in Sublime Text 3 by opening the Command Palette (super + shift + p) and typing JsPrettier: Format Code.
Customizing
You can use .prettierrc for overriding some options, e.g to use semistandard:
{
"semi": true
}Ignoring Files
You can use .prettierignore file for ignoring any files to format, e.g:
dist
.next
**/*.tsAPI
prettier-standard exposes the same API as prettier: https://prettier.io/docs/en/api.html
It also exposes one additional method that works similarly to its CLI:
run(cwd, config)
- cwd - path where to execute prettier-standard
- config - object configuring execution
- patterns - patterns to use for formatting files (array of strings)
- check - whether to check instead of format files (boolean, default: false)
- onProcess - callback that is called for each processed file matching pattern: { file, formatted, check, runtime }
LICENSE
MIT