Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

npm outdated: clarify package name colors in output #16224

@tunderdomb

Description

@tunderdomb

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

Running npm outdated in a color enabled terminal prints you a nice color coded table of your outdated packages. However it's not clear what red and yellow package names mean.
Reading the docs doesn't reveal the difference either. The only place I found mention of this is #4176.

My first impression was this:

  • red: the package is really-really outdated, and updating it would probably bring in a breaking change
  • yellow: the package is outdated, but updating is fine

Actually it means the opposite.

Highlighting this in the docs would help, would you accept a PR with some text about the output colors?

How can the CLI team reproduce the problem?

run npm outdated in a package where dependencies are out of date.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions