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

mortyparse

v1.0.3

Published

Multipart/form-data parser

Downloads

11

Readme

Mortyparse

Parse a Buffer containing a multipart/data-form

Usage

Grab the boundary from the content-type in the POST request and create and instance of Mortyparse.

Then, with the base64 string from the body-json, use the Mortyparse instance to parse the form-data into a readable format.

const Morty = require('mortyparse');                                           
const b64_str = '<base64 string>'; //containing the multipart/form-data as received in the server

morty = new Morty(Buffer("------WebKitFormBoundaryaVKetDdeBHAjicUm"));
let parsed = morty.parse(Buffer(b64_str, 'base64'));

console.log(parsed); // =>
// [
//   {
//     "content_type": "application/pdf",
//     "data": Buffer <37 80 68 . . . 33 13 10>,
//     "filename": "testpdf.pdf",
//     "name": "cv"
//   },
//   { "name": "name", "data": "Test Name"},
//   { "name": "email", "data": "[email protected]"},     
//   { "name": "telephone", "data": "0101010101"},
//   { "name": "vacant", "data": "Back-End"}
//   { "name": "reference", "data": "internet"},
//   { "name": "portfolio", "data": "No aplica"}
// ]

Output format

The parser returns an array containing an object per input in the form.

All inputs in the parsed data will have:

  • name: with a String representing the name of the input field
  • data: with a String|Buffer representing the content of the input
    • Buffer in the case of file inputs
    • String in the case of other inputs

File type inputs will also have:

  • content_type: with a String representing the file format type
  • filename: with a String containing the file name