-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate Remix ESLint Config #7056
Comments
I think a plugin for Remix specific stuff would be great, with a default config, but the config is not related to Remix so it makes sense to deprecate it |
@brophdawg11 Would this mean we have no ESLint setup at all anymore in the templates? |
I believe that's where we're leaning. Templates are not meant to be opinionated - they're meant to be the simplest way to spin up a working Remix app. ESLint is, by design, quite opinionated so we'd like it to become a stacks choice. Even then we want the stacks to make very few choices and rely on best practices in the form of "recommended" presets. Then app teams are free to modify as needed once they create their app from a stack. |
Also remove the remix configs per remix-run/remix#7056
As a relative newcomer to modern JavaScript without a real code style of my own when I started using Remix, I appreciated the eslint plugin. |
The stacks have been converted to simpler ESLint configs and no longer depend on |
about
Currently, can the configuration of The template used in this is Although the file extension of eslint.config.js is js, it appears to be esm and cannot import This is my first attempt at remix. I would like to ask if it is safe for me to develop and use it in a production environment without introducing @remix-run/eslint-config into my eslint system? many thanks 🫡
|
Yes, you do not need |
PR to remove this dependency from the templates: #7597 |
ESLint is an opinion, that's more stacks territory than Remix territory.
Chatted with Michael and we think we should
@remix-run/eslint
config in v2 with a warning on installThe text was updated successfully, but these errors were encountered: