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
Expected behavior
We should use the official Core configurations when possible.
Screenshots
N/A
System information (please complete)
OS X
Browser Chrome
Version Latest
Additional context
I was just cruising through the package.json to see what all was included by default and looking up what each pacakge does and noticed the deprecated message for eslint-config-wordpress
The text was updated successfully, but these errors were encountered:
FWIW I switched to @wordpress/scripts and got a message:
+ @wordpress/[email protected]
added 1354 packages from 713 contributors and audited 890144 packages in 78.885s
found 13000 high severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
So I'm not sure how we'd want to handle that, but it's all a dev dependency so maybe it's not as severe as NPM says?
We're using @wordpress/scripts in Genesis now and I'd be happy to use it in Sample too.
The WP core team periodically runs npm audit fix to fix those warnings, and they're dev dependencies too as you say, so I'm happy to continue down this path.
Describe the bug
eslint-config-wordpress has been deprecated in favor of the official core packages @wordpress/eslint-plugin or @wordpress/scripts
To reproduce
Steps to reproduce the behavior:
Expected behavior
We should use the official Core configurations when possible.
Screenshots
N/A
System information (please complete)
Additional context
I was just cruising through the package.json to see what all was included by default and looking up what each pacakge does and noticed the deprecated message for eslint-config-wordpress
The text was updated successfully, but these errors were encountered: