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 Dec 16, 2019. It is now read-only.
npm has removed support for "engineStrict": true in package.json and what you put in engines in package.json is purely advisory.
Unfortunately, Yarn went in a opposite direction and actually enforces the check unless you pass the --ignore-engines flag. This means people with the latest yarn installed are unable to yarn add angularjs-dropdown-multiselect until they learn about this flag.
Example of the error:
$ yarn add angularjs-dropdown-multiselect
yarn add v0.19.1
[1/4] Resolving packages...
[2/4] Fetching packages...
error angularjs-dropdown-multiselect@1.10.2: The engine "node" is incompatible with this module. Expected version "0.10.10".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
So, I think the engines field of package.json should either removed completely or at least relaxed to the following:
"engines": {
"nodes": ">=0.10.10"
}
The text was updated successfully, but these errors were encountered:
npm has removed support for
"engineStrict": true
in package.json and what you put in engines inpackage.json
is purely advisory.Unfortunately, Yarn went in a opposite direction and actually enforces the check unless you pass the
--ignore-engines
flag. This means people with the latest yarn installed are unable toyarn add angularjs-dropdown-multiselect
until they learn about this flag.Example of the error:
So, I think the engines field of
package.json
should either removed completely or at least relaxed to the following:The text was updated successfully, but these errors were encountered: