npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pmconverter

v1.0.2

Published

By specifying the paths of your collection and environment JSON files, you can update your Postman Collection environments

Downloads

16

Readme

This package helps you change your Postman collections' environment just by specifying the paths of the folder or your collection and environment JSON files.

You can mention:

  • One collection and one environment JSON
  • One collection and many environment JSON files or vice versa
  • Many collections and many environment JSON files

You can also put all of them in one or separate folders and mention folder directories.

The order of the paths (collection and environment or folder) does not matter. Keep in mind: You have to name your environment subdomain as envSubdomain, base URL as a baseUrl, and if you are using API to generate a token then have to name it as tokenUrl and token as a accessToken

Usage:

To use the package, first, you need to install it by running the command:

npm i -g pmconverter
pmconvert <your-collection-path> <your-environment-path>
pmconvert <your-collection-path> <your-environment-path> <your-environment-path>

Or

pmconvert <your-collection-path> <your-collection-path> <your-environment-path>

As mentioned above, the order does not matter:

pmconvert <your-collection-path> <your-collection-path> <your-environment-path>
pmconvert <your-collection-path> <your-collection-path> <your-collection-path> <your-environment-path>
pmconvert <your-folder-path>

Or

pmconvert <your-collection-folder-path> <your-environment-folder-path>