JohnnyMorganz

> @JohnnyMorganz I'd like to tackle this issue if you don't mind, but I think I'll need some help to start. Can we discuss about the solution? @wesleimp I'm definitely...

Having thought I while about this, I agree that this sort of feature probably belongs in a separate tool. The added bloat to stylua is large, and I don't think...

This is somewhat related to #169, and it is quite hard to solve with the current way StyLua works. Fixing this and #169 will require a large overhaul of formatting...

The npm package is just a library which can be integrated into other projects - it does not run the executable itself. The CLI has a lot of logic in...

Alternatively, you can follow one of the other installation steps yourself to install the binary. Not sure if npm exposes a nice way (or if there is a simple helper...

Not sure how husky works, but for the time being if you're interested you could probably make a wrapper yourself which automatically installs a prebuilt binary from https://github.com/JohnnyMorganz/StyLua/releases/tag/v0.14.0 With this,...

> We had talked about using foreman in the extension previously. I think that may be a good way to handle this overall. A large majority of users of stylua...

> I think its a bit out of scope for a formatter to do version management. The suggestion wasn't to manage the version itself, merely provide a warning if it...

When you run `stylua -c path/to/file.lua`, is the `.styluaignore` in the cwd you are running from? I remember a similar issue a while ago that was resolved, https://github.com/JohnnyMorganz/StyLua/issues/249. I wonder...

The VSCode extension looks for `.styluaignore` in the root of the currently open workspace (it has to implement its own ignore detection as it just passes in file content through...