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
As a packaging dependency, bower is not required for rolex to run properly. (Our project uses Webpack/Browserify.). As of May 2017 bower has been deprecated as per Issue #2298 .
Lastly, and perhaps most importantly, if you run npm ls it will fail with a non-0 exit code if unfulfilled peerDepdencies are found, such as with rolex. Perhaps only an annoyance, but if you use npm ls to check the consistency of your build tree as part of a deployment pipeline, this error becomes more significant.
Is there anyway to remove the bower reference from your peerDependency ?
The text was updated successfully, but these errors were encountered:
Rolex specifies
bower
as apeerDependency
.As a packaging dependency, bower is not required for
rolex
to run properly. (Our project uses Webpack/Browserify.). As of May 2017 bower has been deprecated as per Issue #2298 .Lastly, and perhaps most importantly, if you run
npm ls
it will fail with a non-0 exit code if unfulfilledpeerDepdencies
are found, such as withrolex
. Perhaps only an annoyance, but if you usenpm ls
to check the consistency of your build tree as part of a deployment pipeline, this error becomes more significant.Is there anyway to remove the
bower
reference from your peerDependency ?The text was updated successfully, but these errors were encountered: