npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

multipart-browser-parser

v1.0.0

Published

Parse multipart response in browser

Downloads

45

Readme

multipart-browser-parser

npm version MIT License

Got an obscure REST endpoint that returns a multipart response and need to parse it directly in browser? This is the package you are looking for! One response in, multiple responses out.

Installation

Install using npm

  npm install multipart-browser-parser

Example

import {parseMultipartResponse} from "multipart-browser-parser";

async function getMultipartData() {
  let response = await fetch("/api/multipart");
  let {bodyParts} = parseMultipartResponse(response);

  let firstPartAsText = await bodyParts[0].text();
  let secondPartAsJson = await bodyParts[1].json();

  return [firstPartAsText, secondPartAsJson];
}

API Reference

parseMultipartResponse

parseMultipartResponse(response, userOptions?): Promise<ParseResult>

Parse a multipart Response object into separate Response objects

Parameters

| Name | Type | Description | | :------ | :------ | :------ | | response | Response | Multipart Response object | | userOptions? | Partial<Options> | User-supplied parser configuration |

Returns

Promise<ParseResult>

Separate Response objects, together with any raw preamble and epilogue data


parse

parse(body, boundary, userOptions?): ParseResult

Parse raw multipart data into separate Response objects

Parameters

| Name | Type | Description | | :------ | :------ | :------ | | body | ArrayBuffer | Uint8Array | Multipart raw data | | boundary | string | Multipart boundar string | | userOptions? | Partial<Options> | User-supplied parser configuration |

Returns

ParseResult Separate Response objects, together with any raw preamble and epilogue data


getBoundary

getBoundary(headerWithBoundary): string | undefined

Parse a boundary string out of a header that contains it as a parameter

Parameters

| Name | Type | Description | | :------ | :------ | :------ | | headerWithBoundary | string | Raw header value or whole raw header |

Returns

string | undefined Multipart boundary string


ParseResult

Result of parsing of multipart data

bodyParts: Response[]

Separate Response objects parsed from multipart data

preamble: Uint8Array

Raw data of any preamble present in multipart body

epilogue: Uint8Array

Raw data of any epilogue present in multipart body


Options

User-supplied parser configuration

rfcViolationNoBoundaryPrefix: boolean

Flag to set if the Content-Type header already contains

rfcViolationNoFirstBoundary: boolean

Flag to set if your response does not contain a preamble and starts with the first part immediately, without a boundary string


License

MIT