Tim Kevin Oxley
Tim Kevin Oxley
`standard` doesn't have to do everything. A package.json script that runs `prettier` then `standard --fix` should solve your problem and requires no changes to `standard` at all.
@3rd-Eden how'd you go
Hm, has the npm path lookup algorithm changed? Seems weird that it would pick that up. If you are just using this from the command line, try using `npx eslint`...
What version of node?
Ok so I had to pull the execSync polyfill due to a security issue reported in #16, will have to look into alternatives for windows, at least getting this running...
Feel free to do some investigation and send a PR, might be a few days until I get around to looking at it.
@eight04 so hang on, does adding `shell: true` fix the issue?
> Is this module just as capable? This module is really just: 1. set me up the correct npm $PATH 2. exec shell command with $PATH set in the env...
I'd really like to see every npm command be a self-contained module. npm becomes just a container for integration.