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
Do you want to request a feature or report a bug? Feature
What is the current behavior?
check command uses internal resolution mechanism to verify node_modules correctness.
If there is a bug in resolver then install will install node_modules incorrectly and check will fail to identify it.
New behavior
yarn check --commonjs
We need an option for "correctness" check that makes sure that node_modules is consistent with Node.js requirements independent from Yarn's resolver.
For example (#1933), React Native node_modules installed by Yarn 0.16.1 is considered incorrect by check from Yarn 0.17.4.
However node_modules is correct from Node.js resolution point of view (is it? the tests did not catch it).
This will be a good feature for e2e "correctness" checks of Yarn
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
check
command uses internal resolution mechanism to verify node_modules correctness.If there is a bug in resolver then
install
will install node_modules incorrectly andcheck
will fail to identify it.New behavior
yarn check --commonjs
We need an option for "correctness" check that makes sure that node_modules is consistent with Node.js requirements independent from Yarn's resolver.
For example (#1933), React Native node_modules installed by Yarn 0.16.1 is considered incorrect by
check
from Yarn 0.17.4.However node_modules is correct from Node.js resolution point of view (is it? the tests did not catch it).
This will be a good feature for e2e "correctness" checks of Yarn
The text was updated successfully, but these errors were encountered: