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
WARN Failed to find "/fsevents/2.3.2" in lockfile during hoisting. Next aliases will not be hoisted: fsevents
Assuming this is a warning about fsevents not installing because it is an optional dependency that isn't compatible with linux:
(otherwise, bug report for this warning, then?)
Older versions of npm used to show a similar warning, but in npm v7 this warning was removed.
I would like to silence this warning. Best case scenario I would love to see no indication that fsevents was skipped.
This warning adds noise to every single add/remove/install command. I tried pnpm.neverBuiltDependencies but that didn't seem to help.
I used to use yarn, and in that you still get the warning, but there it is an info, and much more subdued.
On Yarn you can also disable this warning entirely with echo "--ignore-platform true" > .yarnrc.
WARN Failed to find "/fsevents/2.3.2" in lockfile during hoisting. Next aliases will not be hoisted: fsevents
Assuming this is a warning about fsevents not installing because it is an optional dependency that isn't compatible with linux:
(otherwise, bug report for this warning, then?)
Older versions of npm used to show a similar warning, but in npm v7 this warning was removed.
I would like to silence this warning. Best case scenario I would love to see no indication that fsevents was skipped.
This warning adds noise to every single add/remove/install command. I tried pnpm.neverBuiltDependencies but that didn't seem to help.
I used to use yarn, and in that you still get the warning, but there it is an
info
, and much more subdued.On Yarn you can also disable this warning entirely with
echo "--ignore-platform true" > .yarnrc
.To repro:
pnpm init -y && pnpm add rollup
(or any package that has an optional dependency on fsevents)The text was updated successfully, but these errors were encountered: