ProxymanApp / ProxymanApp/Proxyman
Support npm packages in Proxyman Scripting require()
Open
@NghiaTranUIT is already working on this.
Since May 5, 2026.
✅ Done
enhancement
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Allow Proxyman Scripting users to install common npm packages and load them through the existing require() workflow.
High-Level Scope
- Keep the existing
require()experience backward compatible. - Support common pure JavaScript npm packages installed for Proxyman scripting.
- Preserve clear safety boundaries for unsupported Node runtime features, native add-ons, and system-level modules.
- Provide a practical user workflow for installing and using packages.
Acceptance Criteria
- Users can install and use popular packages such as date, formatting, validation, and utility libraries in scripts.
- Installed packages can run during real proxy request/response scripting flows.
- Existing built-in libraries and file import behavior continue to work.
- Unsupported packages fail with a clear, user-facing message.
- Documentation includes a simple installation command and sample script.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.