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
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
If so, I don't think that is a case we should worry about supporting. In the unlikely event they are using multiple @neutrinojs/* lint presets, they should just list them all at the start.
Presets such as `@neutrinojs/web` and `@neutrinojs/react` check to
see if a `lint` rule is defined, and if so, adapt its settings to
suit the particular environment/framework. This means that the lint
presets must be defined prior to the compile presets or the final
eslint configuration will not be correct.
Previously if the ordering was incorrect there would be no error
message, causing confusion when eslint wasn't behaving as expected.
Fixes#800.
Refs #763.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As seen in #763 and elsewhere, if the linter presets are included after the other presets, then they don't work as expected.
To help make this case more obvious to users, it seems to make sense for the lint presets to throw if not declared first. eg in eslint preset:
The text was updated successfully, but these errors were encountered: