You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuration Files - use a JavaScript, JSON or YAML file to specify configuration information for an entire directory and all of its subdirectories. This can be in the form of an .eslintrc.* file or an eslintConfig field in a package.json file, both of which ESLint will look for and read automatically, or you can specify a configuration file on the command line.
Existing Behavior
tslint-to-eslint-config will only look at .eslintrc.js by default if not explicitly told a path.
Not so tricky part, just read the package.json file and check if it has the key eslintConfig using the resolveJsonModule compiler option to read json files.
This read should be the fallback behaviour in case of missing .eslintrc.* file, otherwise, throw an error.
🚀 Feature Request
Following #58, https://eslint.org/docs/user-guide/configuring states:
Existing Behavior
tslint-to-eslint-config
will only look at.eslintrc.js
by default if not explicitly told a path.tslint-to-eslint-config/src/cli/runCli.ts
Line 44 in 2b48234
Change Proposal
Add a function dependency to
runCli
that determines the initial script path for ESLint, such as.eslintrc.js
,.eslintrc.yml
.The tricky part here will be supporting
package.json
eslintConfig
...The text was updated successfully, but these errors were encountered: