kjepsonVF
December 13, 2017, 6:35pm
1
Hello Postman Community,
I would like to see if anyone has a solution to an issue I am facing when trying to leverage 3rd party libraries.
The proposed solution I have found in stack overflow and the postman bog and other places is to use eval on the library (saved as a variable) in order to use this. (http://blog.getpostman.com/2015/09/29/writing-a-behaviour-driven-api-testing-environment-within-postman/ )
I was able to get this to work on the chrome app, but when I try to use this method on the desktop app it does not work.
Does anyone have a solution for this?
aksbenz
December 13, 2017, 10:13pm
2
Is there any error ?
kjepsonVF
December 15, 2017, 2:42am
3
Hey @aksbenz - I was able to figure this out! I made a few small mistakes.
shamasis
December 17, 2017, 8:48pm
4
@kjepsonVF - welcome to postman community. I’m glad you could resolve the issue. I’m curious though what mistakes were they. Maybe knowing that would help others from making the same and maybe for us to ensure the docs and usage is clear.
kjepsonVF
December 18, 2017, 3:14pm
5
@shamasis - Yes, I will document this and post a small collection so that others can see the mistake and the solution.
A bit busy this morning, but I should have time this afternoon or tomorrow to get this up!
1 Like
Hey everyone
We have released support for external packages in the latest version of Postman, you can read more about this here:
opened 03:41PM - 11 Apr 25 UTC
product/api-client
external-packages
We’re excited to announce a powerful new capability in Postman’s scripting envir… onment — support for **external public packages from the [NPM](https://www.npmjs.com/) and [JSR](https://jsr.io/) registries**! 🎉
With this release, you can now seamlessly supercharge your pre-request and post-response scripts using your favorite open-source packages right from inside Postman.
## 📽️ Feature Walkthrough
Getting up and running is easy:
1. Open the **Scripts** tab (Pre-request or Post-response) for any HTTP Request.
2. Click on the **Packages** dropdown to search and select a package from **NPM** or **JSR**.
3. Or, directly import packages into your script using [pm.require](https://learning.postman.com/docs/tests-and-scripts/write-scripts/postman-sandbox-api-reference/#import-packages-from-scripts). Examples:
```js
// From NPM
const lodash = pm.require("npm:[email protected] ");
// From JSR
const shortUUID = pm.require("jsr:@opensrc/short-uuid")
```
https://github.com/user-attachments/assets/c39c4951-f92d-4477-8b68-f2a573c80141
> đź“š Read the [full documentation here](https://learning.postman.com/docs/tests-and-scripts/write-scripts/packages/external-package-registries/) for more examples, caveats, and advanced usage.
## 🛠️ Planned Work Ahead
We’re just getting started! Here's what we're working on next:
- **Adding auto-suggestions** in the scripts tab for packages you import — making it even easier to discover and use package APIs as you type.
- **Extending package support across all protocols**, including gRPC, GraphQL, etc.
- **Bringing this feature to Postman CLI and Monitors** so your workflows stay consistent across all Postman tools.
Stay tuned! đź’Ą
## ⚠️ Known Limitations
While this is a huge leap forward, here are a few limitations to be aware of:
- Postman's script environment is platform-agnostic. This means Packages that rely on [Node.js built-ins](https://nodejs.org/api/modules.html#built-in-modules) like `child_process` or `worker_threads` may not work as expected. We offer best-effort implementations of Node built-ins, but they may not have complete parity with Node.js.
- Packages that reference globals outside the [allowed sandbox environment](https://learning.postman.com/docs/tests-and-scripts/write-scripts/postman-sandbox-api-reference/#use-global-objects) may not behave correctly, depending on the part of the package that is executed.
- Packages that use Top-level `await` are not supported at the moment.
## 🙌 Thank You!
This was long overdue and wouldn’t have been possible without the incredible feedback and support from our Postman community. Your insights and use cases helped shape this—please keep it coming!
Happy Scripting!
,