(feat): Include 'npm outdated'

[kuncevic]

Thank you for your work.

I was wondering if the report could also include the results from npm outdated so we have a complete view of the project dependencies.

[TaylorHo]

Yes, it would definitely be great to have! I'll keep this on track to develop as soon as possible.

[TaylorHo]

Hello @kuncevic!

I’ve been thinking about possible ways to support this feature. Right now, the tool only works by piping the output of another command, e.g.:

npm audit --json | audit-export

Because of this, we don’t currently have access to npm outdated results.

I see a few potential approaches:

1. Let the CLI run the commands itself

• The CLI would directly run npm audit / npm outdated instead of relying on piping.
• This would mean a breaking change in syntax, since users wouldn’t be piping JSON anymore.
• Auto-detecting the package manager (npm, pnpm, yarn, bun, etc.) could also be tricky.
• We could keep backward compatibility by continuing to support the old piping style.

2. Hybrid approach (pipe + parameter)

• Users still pipe the audit output.
• If they also pass an --outdated flag, the CLI infers the package manager (from the audit JSON) and runs the corresponding outdated command internally.

3. Support multiple pipes

• Allow both commands to be piped separately:

  npm audit --json | audit-export  
  npm outdated --json | audit-export  

• Instead of one overwriting the other, the CLI would merge results:

  • If it sees audit data first, then outdated data, it appends that section.
  • The final report includes both.

---

What do you think about these options? Which direction do you feel would make the tool easier to use and maintain?

[kuncevic]

Hey @TaylorHo this suggestion looking great npm outdated --json | audit-export sounds like the best way to go.

[TaylorHo]

Great, thanks @kuncevic. We will implement this feature this way!