Steven Zeck

It shouldn't matter. All it does it reports the coverage results of `npm test` (I think all repos use that command) from Travis to CodeClimate, not much overhead.

Yep, that's the second checkmark https://github.com/Unibeautify/unibeautify/issues/204#issuecomment-429361164

* Editors will need to provide some info: Version information such as atom, apm, electron, npm, etc. * Stack traces, would they come from editors or Unibeautify core? Or both?...

Right, Unibeautify core would just be responsible for gathering the information and generating the JSON. Assistant would read it and guide users through the issue.

Winston 3.x also has native typings, no having to use @types.

Does log4js-node output to the console as well without the need to do event listeners and/or callbacks?

I have a POC in https://github.com/szeck87/atom-beautify/blob/unibeautify/src/logger.ts. It's messy, I hope it can be cleaned up once the typings for Winston 3.x are available. I'm disappointed there isn't a standard transport...

I don't see an option in prettier to add HTML tags to unformatted. Your best bet is to use comments so Unibeautify ignores those sections: ``` ```

@SilentImp I think what you want is https://www.npmjs.com/package/unibeautify. You can call the methods in there using node. Docs here: https://api.unibeautify.com/

https://github.com/Unibeautify/vscode/blob/master/src/EditProvider.ts#L52-L86 is a good example. Mainly https://github.com/Unibeautify/vscode/blob/master/src/EditProvider.ts#L80-L83, you'll see that's where `unibeautify` calls the `beautify` method with the data (text, language, options, etc).