We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I know we’re using Yarn—why again? But still, should the deprecated dependencies called out by npm i be evaluated?
npm i
npm WARN deprecated [email protected]: Deprecated in favour of eslint-config-wikimedia. -- https://phabricator.wikimedia.org/T118941 npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info. npm WARN deprecated [email protected]: no longer maintained
Travis uses npm to install.
Node.js v11.1.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I know we’re using Yarn—why again? But still, should the deprecated dependencies called out by
npm i
be evaluated?Travis uses npm to install.
Node.js v11.1.0
The text was updated successfully, but these errors were encountered: