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
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
yarn is more fussy about peer dependencies than npm, in that it doesn't take into account that dependencies are being hoisted, so warns if a peerDependency is not explicitly specified at the top level (see yarnpkg/yarn#4675).
Some of the Neutrino packages trigger this case, so result in noisy yarn warnings that don't mean anything is broken, but that can confuse the user (and results in things like Heroku's nodejs buildpack outputting an extra warning suggesting it might be the cause of problems).
Whilst this is isn't our fault we should add some additional (duplicate) dependency declarations to avoid these warnings.
Yarn doesn't take into account hoisting when displaying unmet peer
dependency warnings, so this adds explicit top-level dependencies
on packages that were being pulled in via sub-dependencies.
Fixes#751.
yarn is more fussy about peer dependencies than npm, in that it doesn't take into account that dependencies are being hoisted, so warns if a
peerDependency
is not explicitly specified at the top level (see yarnpkg/yarn#4675).Some of the Neutrino packages trigger this case, so result in noisy yarn warnings that don't mean anything is broken, but that can confuse the user (and results in things like Heroku's nodejs buildpack outputting an extra warning suggesting it might be the cause of problems).
Whilst this is isn't our fault we should add some additional (duplicate)
dependency
declarations to avoid these warnings.The text was updated successfully, but these errors were encountered: