Promoting eslint-define-config?
#8802
Replies: 4 comments
-
|
Hi 🥰 |
Beta Was this translation helpful? Give feedback.
-
|
TL;DR - I think that migrating off of The big reason that I didn't want us to get into hosting and owning the With flat configs we now have one major thing that we didn't have before: all plugins and configs are imported into the config file. This means that there's no longer a triple-slash-ref requirement and we can extract types directly from the package (or perhaps an So with this we can document a solution and release tooling that allows a plugin to generate a type signature as a build step that we can then extract (using the That was actually a big part of the reason that I chose to release the |
Beta Was this translation helpful? Give feedback.
-
|
Yesterday I did my first steps with eslint v9 & FlatConfig Using the So What do you think about this @bradzacher? |
Beta Was this translation helpful? Give feedback.
-
|
Just as a note, I deprecated |
Beta Was this translation helpful? Give feedback.
-
Body
Hey Guys 👋
I know I'm late for the party, because
tseslint.config()was introduced more than a month ago, but I wanted to ask regardless what do you think about using eslint-define-config for declaring the ESLint config in a type safe manner?I feel like @Shinigami92 did a great job with that library and it would be great to join forces with him to have a de-facto solution for type-safe configurations. It feels like we have two competing solutions now with the introduction of the aforementioned
tseslint.config()function.Related discussion: #6090 (I didn't know whether to comment there, or start a new thread, I'm happy to close this and move the discussion there)
Before you submit your discussion, please confirm the following. If any of these required steps are not taken, we may not be able to review your RFC. Help us to help you!
Beta Was this translation helpful? Give feedback.
All reactions