A local workspace
Collections and environments remain inspectable files. The server binds locally rather than acting as a public multi-user service.
DEVELOPER TOOLS / released
PacketLark
A local workbench for requests, tests and API discovery.
The problem.
API development needs more than a Send button: repeatable requests, inspectable traffic and tests that travel with the workspace.
My contribution.
Built the local API product across its browser interface, HTTP engine, workspace persistence, isolated scripting, CLI integrations and packaging.
How the parts connect.
Interface
Compose requests, inspect responses and organize collections and environments.
HTTP engine
Local forwarding, cookie sessions and isolated QuickJS test scripts.
Workspace files
Readable resource files with ownership and conflict reconciliation.
The decisions.
Separate script execution
QuickJS isolates imported scripts from Node object references with resource limits and a narrow bridge.
Build, test, deliver.
Supported HTTP workflows, setup and limitations.
Configured Node 22/24 build, tests and package checks.
Installation guide and labelled sample preview.
What to keep in mind.
The published GitHub Pages website is a product site/sample preview; it does not run the Node workbench.
Not a complete Postman replacement. Protocol clients, cloud collaboration and some recovery workflows remain outside current scope.