w0rp
|
e6745a3811
|
Fix #1989 - Use ESlint options for fixers too
|
2019-05-17 20:45:25 +01:00 |
|
w0rp
|
3bebcb5d48
|
#2132 - Replace command_chain and chain_with with ale#command#Run
|
2019-04-07 14:58:06 +01:00 |
|
w0rp
|
ddb3e6d57a
|
Handle failing to connect to eslint_d
|
2018-09-17 17:32:57 +01:00 |
|
w0rp
|
1568bf8128
|
Fix the mscs tests on Windows, and use the improved Simplify for all tests instead.
|
2017-12-19 18:23:09 +00:00 |
|
w0rp
|
6503b85d3d
|
Fix #1178 - Don't use the output from eslint_d for fixing files when the output is an error message
|
2017-11-29 10:08:54 +00:00 |
|
w0rp
|
5160f814d9
|
Fix #988 - Support --fix-dry-run for ESLint by processing the JSON output
|
2017-11-22 23:23:14 +00:00 |
|
w0rp
|
9857e0a4b7
|
Fix the eslint_d fixer tests for Windows
|
2017-11-22 17:25:37 +00:00 |
|
w0rp
|
6e65998ca7
|
#988 Take --fix-dry-run away again, because it is dumb
|
2017-11-22 17:01:50 +00:00 |
|
w0rp
|
b5ec1a5fd0
|
Fix #988 - Support --fix-dry-run for ESLint where available, and --fix-to-stdout for eslint_d
|
2017-11-22 16:51:04 +00:00 |
|
w0rp
|
5091e2de45
|
Get fixer tests to work on Windows
|
2017-10-01 20:23:41 +01:00 |
|
Ray Zane
|
cb56cbb714
|
There seems to be a bug in eslint that causes the --config option to
not detect node_modules correctly. The `-c` option, however, works fine.
|
2017-09-24 13:57:18 -04:00 |
|
w0rp
|
661ed6e40b
|
Fix #923 Use package.json as a last resort for eslint --fix
|
2017-09-12 09:10:37 +01:00 |
|
w0rp
|
8eb99c3cec
|
Fix #922 - Prefer nearer ESLint configuration files with lower precedence filenames for eslint --fix
|
2017-09-11 21:53:45 +01:00 |
|
w0rp
|
7c2a5052a8
|
Fix #895 - Run Node.js scripts with node.exe instead of node on Windows
|
2017-08-31 13:12:24 +01:00 |
|
w0rp
|
0931e99ea4
|
Fix #775 - Run eslint.js via node on Windows for eslint --fix
|
2017-07-18 12:28:20 +01:00 |
|