-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like esformatter is not installed. Please make sure that it is installed globally or in project node_modules folder #75
Comments
are you using |
macos 10.12.3 node installed with tar.gz . and confing NODE_HOME ... |
Python Anyway, in both cases you can try setting the
point it to your global installation of |
the above did not seem to work. neither setting the path to |
Did you install it with nvm or yarn? I don't use sublime anymore, I don't know how to debug this |
i installed with npm, tried brew as well to see if linking differently. how does one use nvm? that's a node version manager |
I had a quick look at the code, the plugin tries to run It also relies on In any case, both this plugin and esformatter are kinda inactive (last commit on esformatter is more than 1 year ago). You might have better luck with |
installed esformater :
npm install -g esformatter
execute command:
esformatter --help
result:
`Usage: esformatter [options] [files...]
Options:
-v, --version Display the current version.
-h, --help Display help and usage details.
-c, --config Path to custom configuration file.
-p, --preset Set style guide preset ("jquery", "default").
--plugins Comma separated list of plugins.
-i Edit input files in place; use with care!
--diff Check code style and output char diff.
--diff-unified Check code style and output unified diff.
--no-color Remove colors from diff (default if terminal doesn't
support colors).
--color Force colored diffs even if terminal doesn't support it.`
but sublime text(3) alert:
It looks like esformatter is not installed. Please make sure that it is installed globally or in project node_modules folder
The text was updated successfully, but these errors were encountered: