Feature Request: Requestly as a VS Code Extension
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vscode
Research direction
The issue names no files, tests, or entry points. Start by surveying the TypeScript repository and its current interceptor architecture, then define the VS Code integration scope and acceptance criteria for rule management, proxy or API tooling, account sync, and local or remote environments.
Written by the indexing model from the issue text.
Description
It would be great to have Requestly available as a Visual Studio Code extension.
Motivation:
Many developers spend most of their time inside VS Code, and having Requestly integrated directly into the editor would streamline debugging and API testing workflows. Instead of switching between the browser and the editor, users could manage rules, mocks, and API modifications from within VS Code.
Proposed Features:
- View, create, and manage Requestly rules inside VS Code
- Integrate with VS Code’s network proxy or API testing tools
- Sync with the user’s Requestly account
- Support for local and remote environments
Benefits:
- Simplifies development workflows
- Reduces context switching between tools
- Makes Requestly more accessible to backend and full-stack developers
Example Use Case:
A developer debugging API responses could mock an endpoint directly from VS Code while coding, without having to switch to the browser extension.
- Dominant language
- TypeScript
- Stars
- 87
- Forks
- 23
- Avg merge
- 14h
- Merged PRs (30d)
- 3
Contributor guide
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.
More from requestly/interceptor
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
requestly/interceptor#121 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
requestly/interceptor#26 · 1 comment ·
-
migration:misfiled-interceptor
Difficulty 5/5 Over a week Newbie friendliness 38/100
requestly/interceptor#27 · 2 comments ·
-
migration:misfiled-interceptor
Difficulty 3/5 1-2 days Newbie friendliness 45/100
requestly/interceptor#28 · 1 comment ·
-
migration:misfiled-interceptor type:bug
requestly/interceptor#29 · 2 comments · 1 assignee ·
All issues in requestly/interceptor
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·