lintText and lintTextSync forcefully interact with the file system API

[sadasant]

Hi team!

We're planning to use standard as a formatting API tool, since we know this repo offers functions such as lintText and lintTextSync. However, our target software does heavy interactions with the file system, and we do heavily mock the file system in our unit tests. I wonder if we could optionally disallow standard to use the file system API for lintText and lintTextSync. What do you people think? 🤔❔

[Flet]

• lintText calls the internal parseOpts function
• this function uses pkg-conf to scan the filesystem for a package.json to look for additional options. This may be the filesystem calls that are happening.
• there may also be additional calls inside executeOnText function in eslint itself (I didn't get a chance to check it thoroughly)

It may be worth using standard-engine directly (with eslint-config-standard) and passing the customParseOpts option to send a modified parseOpts function. This would be a way to avoid the file system call to read package.json. Another option is to just use eslint directly :).

Part of the philosophy of the standard tool is to avoid having lots of configuration. Dropping down to using standard-engine directly may be the fastest way to accomplish your goal.

[feross]

@Flet Maybe we should change standard-engine so that lintText doesn't take into account the package.json settings? It seems pretty random that lintText would behave differently depending on the current working directory.

[Flet]

@feross yeah that makes sense!

[feross]

PR sent: standard/standard-engine#166

@sadasant Can you check if using standard with that PR applied to standard-engine solves your issue?