Registry / aws / aws-lambda-multipart-parser

aws-lambda-multipart-parser

JSON →
library0.1.3jsnpmunverified

This library provides a specialized parser for `multipart/form-data` requests specifically designed for AWS Lambda environments. Unlike general-purpose server-based parsers, `aws-lambda-multipart-parser` is tailored to work within the constraints of serverless functions and the particular event structure provided by AWS API Gateway. It takes the raw `event` object from a Lambda invocation and processes its `body` to extract form fields and uploaded files, returning a structured JavaScript object. The current stable version, 0.1.3, indicates a very early stage of development, and the project appears to be abandoned, with no significant updates or commits in several years. Its primary differentiator was its early focus on simplifying `multipart/form-data` handling for AWS Lambda at a time when native support was less mature, abstracting away the complexities of binary media types, base64 encoding, and API Gateway proxy integration nuances.

awshttp-networkingserialization
npm install aws-lambda-multipart-parser
github ↗package ↗
INSTALL
IMPORT
SIG · AWS-LAMBDA-MULTIPA
A
aws-lambda-multipart-parser
awsjavascriptv0.1.3
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

parse
✓ const parse = require('aws-lambda-multipart-parser');
✗ import parse from 'aws-lambda-multipart-parser';
The library is CommonJS-only and does not natively support ESM import syntax.
parse
✓ const { parse } = require('aws-lambda-multipart-parser');
✗ import { parse } from 'aws-lambda-multipart-parser';
While `parse` is the primary export, destructuring from `require` is common. ESM named imports are not supported.

Demonstrates parsing an AWS Lambda event containing multipart/form-data and returning a structured JSON response, including necessary CORS headers.

const multipart = require('aws-lambda-multipart-parser'); exports.handler = (event, context, callback) => { // Ensure API Gateway is configured for binary media types and Lambda Proxy Integration. // The 'spotText' parameter can be set to true to have text files returned as strings. const parsedBody = multipart.parse(event, true); // Example of accessing a field and a file console.log('Form field value:', parsedBody.field); if (parsedBody.file) { console.log('File:', parsedBody.file.filename, parsedBody.file.contentType); // If spotText is true, content of text files is a string console.log('File content (text):', parsedBody.file.content); } const response = { statusCode: 200, headers: { "Access-Control-Allow-Origin": "*", // Essential for CORS if frontend is different origin "Content-Type": "application/json" }, body: JSON.stringify({ message: "Successfully parsed multipart data", data: parsedBody // Be careful exposing raw parsed data, especially buffers }) }; callback(null, response); };
Debug
Known issues
breakingThis library is effectively abandoned, with no updates or commits in over six years. It may not be compatible with newer Node.js runtimes (e.g., Node.js 18+), latest AWS Lambda features, or API Gateway configurations. Modern alternatives should be preferred.
fix
Consider using newer, actively maintained libraries like `busboy` or implementing custom parsing logic with current Node.js APIs, or leveraging API Gateway's direct integration features for file uploads if applicable.
affects: >=0.1.3
gotchaWhen integrating with API Gateway, it is crucial to set `integration: LAMBDA` in your `serverless.yml` or enable 'Use Lambda Proxy Integration' in the API Gateway console. Failing to do so will result in '502 Bad Gateway' errors.
fix
Ensure your API Gateway method's 'Integration Request' for your Lambda function has 'Use Lambda Proxy Integration' checked, or set `integration: LAMBDA` if using Serverless Framework.
affects: >=0.1.0
gotchaDefault API Gateway CORS configurations do not always work correctly with `LAMBDA` integration for `multipart/form-data`. You must manually include `Access-Control-Allow-Origin` headers in your Lambda function's response.
fix
Add `"Access-Control-Allow-Origin": "*"` (or specific origin) to the `headers` object of your Lambda's response.
affects: >=0.1.0
gotchaThe library returns file contents as Node.js `Buffer` objects by default for non-text files. If `spotText` is `true`, text files are returned as strings. Handling binary buffers correctly (e.g., converting to base64 for JSON responses) is crucial.
fix
When returning file content in a JSON response, convert `Buffer` objects to a base64 string (e.g., `file.content.toString('base64')`). Ensure the client knows how to decode it.
affects: >=0.1.0
Errors
Common errors & fixes
502 Error: Bad Gateway
API Gateway is not configured for Lambda Proxy Integration, or `integration: LAMBDA` is missing in Serverless Framework configuration.
fix
In API Gateway console, for your POST method's 'Integration Request', check 'Use Lambda Proxy Integration'. If using Serverless Framework, add `integration: LAMBDA` to your function's HTTP event configuration.
Access to XMLHttpRequest at '...' from origin '...' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Your Lambda function's response is missing the `Access-Control-Allow-Origin` header required for cross-origin requests.
fix
Include `headers: { "Access-Control-Allow-Origin": "*" }` (or your specific frontend origin) in your Lambda function's response object.
Upgrade
Version history
0.1.3latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
19 hits · last 30 days
node
16
OpenAI (training)
1
Resources
githubhttps://github.com/myshenin/aws-lambda-multipart-parser ↗
packagehttps://www.npmjs.com/package/aws-lambda-multipart-parser ↗
aws-lambda-multipart-parser — npm install aws-lambda-multipart-parser · libregistry