orpc-extend-body-parser

Extend oRPC body parser for larger payloads and custom multipart data.

8|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ali-master/skills --skill orpc-extend-body-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orpc-extend-body-parser
Source: https://github.com/ali-master/skills/tree/main/skills/orpc-extend-body-parser
Command: npx skills add https://github.com/ali-master/skills --skill orpc-extend-body-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of handling larger payloads and additional data types that exceed the standard body parser capabilities.

Core Features & Use Cases

  • Extended Body Parsing: Manages larger payloads and additional data types beyond the standard JSON and form-urlencoded.
  • Custom Multipart Parsing: Allows for custom multipart parsing for non-standard or streaming multipart data.
  • Streaming File Handling: Stream files to disk to reduce memory usage for large file uploads.
  • Use Case: Ideal for scenarios where your application needs to handle large binary files or complex data formats, such as uploading large files or processing multipart/form-data with additional content types.

Quick Start

Extend the body parser for handling large file uploads with the oRPC Extend Body Parser Skill.

Frequently Asked Questions about orpc-extend-body-parser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle large file uploads in oRPC without exceeding memory limits?

To handle large file uploads in oRPC, you can extend the body parser to stream files directly to disk, significantly reducing memory usage for large HTTP payloads. This prevents memory exhaustion.

Can I parse non-standard multipart/form-data formats using oRPC?

Yes, you can parse non-standard multipart/form-data formats by extending the oRPC body parser to support custom multipart parsing for complex data formats and additional content types.

What is the best way to process large binary files in an oRPC application?

The best way to process large binary files in an oRPC application is using an extended body parser to manage larger payloads and stream file uploads directly to disk, bypassing standard JSON limitations.

Does oRPC support custom body parsing for complex HTTP request bodies?

oRPC supports custom body parsing for complex HTTP request bodies through an extended body parser mechanism, enhancing its capability to process a wider range of non-standard input formats and data types.

Why do standard JSON and form-urlencoded parsers fail for large payloads?

Standard JSON and form-urlencoded parsers fail for large payloads because they load entire request bodies into memory, whereas an extended body parser can stream multipart data to disk to reduce memory usage.