summaryrefslogtreecommitdiff
path: root/test/test_eslint_executable_detection.vader
AgeCommit message (Collapse)Author
2021-03-01Close #2281 - Separate cwd commands from commandsw0rp
Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2020-07-08eslint: Use cwd from executable location to fix nested projects (#3222)Kevin Locke
* Split FindNearestExecutable from FindExecutable The path searching in ale#node#FindExecutable() will be useful for eslint. Refactor it into a separate function so it can be used without regard for the state of the _use_global and _executable variables. Signed-off-by: Kevin Locke <kevin@kevinlocke.name> * eslint: Set project root from local executable Using the nearest directory with node_modules does not work correctly for nested projects where the eslint dependencies are in the outer project. For example: https://github.com/dense-analysis/ale/issues/3143#issuecomment-652452362 Adopt the behavior of SublimeLinter, which runs from project_root determined by the presence of the eslint executable in node_modules/.bin (or eslint in dependencies/devDependencies of package.json, which we can add later as necessary). See [NodeLinter#find_local_executable]. [NodeLinter#find_local_executable]: https://github.com/SublimeLinter/SublimeLinter/blob/056e6f6/lint/base_linter/node_linter.py#L109 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
2019-12-17Run ESLint from project root dir where possibleKevin Locke
ESLint 6 loads all plugins/configs/parsers relative to the project root which, by default, is the directory in which ESLint is invoked, as described in [ESLint RFC 2018-simplified-package-loading]. Therefore, ALE should run ESLint from the project root, when possible, so that dependencies will load. This commit does so. [ESLint RFC 2018-simplified-package-loading]: https://github.com/eslint/rfcs/blob/master/designs/2018-simplified-package-loading/README.md Fixes: #2787 Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
2019-06-02Use JSON output for eslint and fix tsserver columnNils Kuhnhenn
2019-04-07#2132 - Implement feature tests with ale#Hasw0rp
2019-04-07#2132 - Replace command_chain and chain_with with ale#command#Runw0rp
2018-08-10Revert "#1459 Always run ESLint in the directory of the file being checked"w0rp
This reverts commit 634bf73f52c9d533476058a9fe464b93eb90f3d8.
2018-08-09#1459 Always run ESLint in the directory of the file being checkedw0rp
2017-12-19Fix the mscs tests on Windows, and use the improved Simplify for all tests ↵v1.7.0w0rp
instead.
2017-10-23Get all tests to pass on Windowsw0rp
2017-08-31Fix #895 - Run Node.js scripts with node.exe instead of node on Windowsw0rp
2017-07-09Make every test set filenames and switch directories in the same way, and ↵w0rp
fix some missing escaping for the rubocop linter
2017-06-20Fix #668 - Support eslint for TypeScriptw0rp
2017-05-26#576 Run the eslint.js file created by React with node on Windowsw0rp
2017-05-25Automatically use eslint_d for eslint, when availablew0rp
2017-05-20Add commands to run ALEFix, and some tests to cover functionality so far. ↵w0rp
Add a simple autopep8 function.
2017-03-29Fix #421 Automatically detect create-react-app pathsw0rp