Skip to content

Tags: jaulz/prettier-eslint-cli

Tags

v4.4.0

Toggle v4.4.0's commit message
feat(cli): add the --stdin-filepath option (prettier#108)

This option is really usefull when using prettier-eslint-cli inside text
editor plugins, to let prettier-eslint discover the correct eslintrc
configuration for the given file.

Related:
* prettier#95
* sbdchd/neoformat#112
* prettier/prettier-emacs#10 (comment)

v4.3.2

Toggle v4.3.2's commit message
fix: add --config option (prettier#104)

v4.3.1

Toggle v4.3.1's commit message
fix: upgrade to prettier@8 (prettier#103)

v4.3.0

Toggle v4.3.0's commit message
feat: update for the prettier-eslint beta (prettier#99)

This package now supports prettier's configuration capabilities

v4.2.3

Toggle v4.2.3's commit message
fix: force dep updates

* WIP: upgrade babel

* cleanup

v4.2.2

Toggle v4.2.2's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
fix: Bumped eslint, prettier-eslint to latest with updates (prettier#97)

* fix: Bumped eslint, prettier-eslint to latest with updates

Bumped eslint to 4.5.0 and prettier-eslint to 6.4.2. Updated eslint-config-kentcdodds to 12.4.2.
Added some changes to package.json to correct new formatting of error rules form eslint.  Imported
Config and Lint from eslint/lib to pass into the new ConfigFile.load(file, context)

fix: update to eslint 4.0 prettier#94

* fix: Fixes after PR Review

Updates after PR Review to move const location

closes prettier#94

v4.2.1

Toggle v4.2.1's commit message
fix: remov default values for eslintPath and prettierPath (prettier#93)

* Removed default values for eslintPath and prettierPath

These values are not required by prettier-eslint-cli itself. They
are only passed to prettier-eslint, and even then, they're optional.
When using npm >3, passing the default value is optional, since
the node_modules directory is flattened, but for npm 2.x, the
default assumptions don't work.

People should be running npm >3 today, but for CI scenarios, npm 2
or downwards can still be used in combination with node 4.x (which
is going to be supported for a long time still).

In any case, not passing a default value seems to align better with
node's require algorithm - it will start where it needs to start
(in this case wherever the prettier-eslint dependency has been
installed), and then mimick find-up's logic.

* Removed superfluous imports

v4.2.0

Toggle v4.2.0's commit message
feat(options): allow specifying eslint configuration file as an argum…

…ent (prettier#91)

* feat(options): allow specifying eslint configuration file as an argument

closes prettier#37

* test(options): add stub test for eslintConfigPath option

* Update .all-contributorsrc

v4.1.1

Toggle v4.1.1's commit message
fix(CLI): --list-different: error out there are differences (prettier#78

)

* docs(contributor): new contributor

* fix(cli): --list-different: error out when contents has changed

v4.1.0

Toggle v4.1.0's commit message
feat(logging): Respect logLevel.SILENT when logging formatted file ch…

…anges (prettier#74)

* feat(logging): Respect logLevel.SILENT when logging formatted file changes

We now respect the logLevel when logging out the results of files that have been changed by
`format-files`. Previously even if the log level was silent we still logged this out.

* Contributor

* ESLint warning