Feature request: Export packages in postman to reuse code and run in newman

[varsharyalii]

Title: Feature Request: Add package.json Support in Newman for Package Management

Description:

Hi Team,

I’m a frequent user of Newman CLI in my CI/CD pipelines and would like to request support for package.json to improve dependency management. I understand that Newman is a separate project from Postman, and currently, the package library is not supported. However, being able to manage and install external dependencies through a package.json would greatly benefit users like me who rely on Newman for automating Postman collections.

Currently, the package library available in Postman’s UI cannot be used in Newman, and I have encountered situations where external packages (e.g., lodash, moment) would simplify our scripts. Having support for package.json would streamline this process by:

Benefits:

• Centralized Dependency Management: Users can declare all necessary packages in package.json, similar to Node.js projects.
• Version Control: Teams can manage and lock versions of external packages to avoid inconsistencies.
• Enhanced CI/CD Workflows: Easier integration with existing CI/CD pipelines that already rely on package.json for package management.
• Automation: Newman could automatically install dependencies defined in package.json before running the tests, reducing manual overhead.

This feature would improve flexibility and efficiency in using Newman with external libraries in test automation.

Thank you for considering this!

[figuedmundo]

+1

[blaubleu]

+1
Particularly for this reason:

Enhanced CI/CD Workflows: Easier integration with existing CI/CD pipelines that already rely on package.json for package management.