Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn ignores the cpu setting in package.json when the engines section does not exist in package.json.
If the current behavior is a bug, please provide the steps to reproduce.
make sure your node's process.arch is not ia32. for example, use a 64bit node on 64bit windows.
in an empty directory, save this as package.json:
now run yarn install. it will finish without showing any errors. this is the bug.
(you can try npm install, and it will show the error correctly)
now replace the content of package.json with this:
{
"cpu": ["ia32"],
"engines": {}
}
and run yarn install. this time it will correctly say that the cpu-setting is incorrect.
What is the expected behavior?
yarn should respect the cpu setting in package.json when the engines setting does not exist.
Please mention your node.js, yarn and operating system version.
node 8.15.0
windows 10
yarn 1.13.0
Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn ignores the
cpusetting inpackage.jsonwhen theenginessection does not exist inpackage.json.If the current behavior is a bug, please provide the steps to reproduce.
make sure your node's
process.archis notia32. for example, use a 64bit node on 64bit windows.in an empty directory, save this as
package.json:now run
yarn install. it will finish without showing any errors. this is the bug.(you can try
npm install, and it will show the error correctly)now replace the content of
package.jsonwith this:and run
yarn install. this time it will correctly say that the cpu-setting is incorrect.What is the expected behavior?
yarn should respect the
cpusetting inpackage.jsonwhen the engines setting does not exist.Please mention your node.js, yarn and operating system version.
node 8.15.0
windows 10
yarn 1.13.0