feat(eslint): allow specifying eslint config file #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add configuration option to pass through to ESLint that will specify a custom path for ESLint to find the configuration file to be used.
This is useful in our situation (legacy project with multiple builds + eslints in the mix) when the root eslintrc file is incorrect for the code that Vite is building. New code is separated in a pseudo monorepo structure so we need to be able to point at a different base eslintrc config file.