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 May 1, 2024. It is now read-only.
I have a monrepo that I manage with NPM workspaces. It contains an internal package at packages/ui and its name in package.json is ui and its version number is 0.0.0 and never changes.
I use the ui package inside the monorepo by adding it as "ui": "*", inside other workspaces.
When I run npm outdated, NPM tells me that I need to upgrade ui to v0.2.4, which is the latest version of an abandoned NPM package.
Shouldn't npm outdated notice that ui is an internal package? Or does NPM workspaces assume that the names of internal packages never conflict with external ones?
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
-
I have a monrepo that I manage with NPM workspaces. It contains an internal package at
packages/ui
and its name inpackage.json
isui
and its version number is0.0.0
and never changes.I use the
ui
package inside the monorepo by adding it as"ui": "*",
inside other workspaces.When I run
npm outdated
, NPM tells me that I need to upgradeui
to v0.2.4, which is the latest version of an abandoned NPM package.Shouldn't
npm outdated
notice thatui
is an internal package? Or does NPM workspaces assume that the names of internal packages never conflict with external ones?Beta Was this translation helpful? Give feedback.
All reactions