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
I try running pnpm up caniuse-lite in my repository, while caniuse-lite is not my direct dependency maybe it is somewhere else in my dependency tree. It seems it updates not only in lockfile (which is expected), but majority package versions in my own package.json is also modified, I'm also not sure the modified package has a direct dependency to caniuse-lite but if it does it is totally make sense for me.
So is this the expected behavior I get when running pnpm up <pkg> to an indirect dependency?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Sorry if this is like a newbie question 🙏🏼
I try running
pnpm up caniuse-lite
in my repository, whilecaniuse-lite
is not my direct dependency maybe it is somewhere else in my dependency tree. It seems it updates not only in lockfile (which is expected), but majority package versions in my ownpackage.json
is also modified, I'm also not sure the modified package has a direct dependency tocaniuse-lite
but if it does it is totally make sense for me.So is this the expected behavior I get when running
pnpm up <pkg>
to an indirect dependency?Beta Was this translation helpful? Give feedback.
All reactions