-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Revert "feat: remove experimental-utils
"
#6602
Conversation
This reverts commit 71adbc5.
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
just to revisit this and have a chat in the open.
#6179 (which causes a console log) on usage will create noise for consumers that have The two options we have are:
Personally I think the former is better because (a) the deprecation message is install-time-only, so it won't spam users' lint runs and (b) hard-locking to v5 means packages can't be lazy - they have to migrate to keep updated. I'd love to hear your thoughts again Josh, maybe @typescript-eslint/triage-team has some thoughts as well? |
(closing for now since it seems this PR isn't particularly popular 😄) |
Reverts #6468
Discussed privately - letting the changes in #6179 live for a little while.