Closed poberlohr closed 6 years ago
You need to quote the path:
`
`
There are no spaces in my path to *.cmd.
The spaces are in the path to the file the linter should check. So in the XML that ESLint returns there are spaces in the path.
I'll post the XML that ESLint creates after the weekend, if that helps
Ow! Thanks! You can download the updated version from sourceforge: https://sourceforge.net/projects/notepad-linter/
Great, it works now, thanks!
I am receiving the following error in Windows 10 64 Bit. Although there is no space in the paths to the cmd file and my JS file.
Linter: Invalid output format. Only checkstyle-compatible output allowed.
I am receiving the following error in Windows 10 64 Bit. Although there is no space in the paths to the cmd file and my JS file.
Linter: Invalid output format. Only checkstyle-compatible output allowed.
You should check the linter ouput, try to type and run command from the command line.
Command line is working perfectly. I have local install of eslint for my project. The path to cmd is D:\node\nodetest2\node_modules.bin\eslint.cmd
Command line is working perfectly. I have local install of eslint for my project. The path to cmd is D:\node\nodetest2\node_modules.bin\eslint.cmd
I have the same issue. No spaces in both the command path and the file path, but linter gives me the same error message.
This is my configuration file:
`<?xml version="1.0" encoding="utf-8" ?>
Same issue here. No spaces in command path or file path
Same issue here.
Could it be due to notepad++ using other-direction slashes for some of the target path /
\
perhaps ?
I also have the same problem. The command line is working just fine
Hi,
I just tried to get this plugin working using ESLint, but I got an error when I opened my file index.js:
After trying this and that for way too long I moved my project folder to
instead of
and it worked, so I think the space in
Eigene Dateien
lets the linter fail.