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

@xxmichas/bussinboy

v2.1.0

Published

A small promise based wrapper for [@fastify/busboy](https://github.com/fastify/busboy) that focuses on ease of use and simplicity.

Downloads

26

Readme

💯 bussinboy

A small promise based wrapper for @fastify/busboy that focuses on ease of use and simplicity.

🛠️ Requirements

  • Node.js >= 18

✨ Features

  • Promise based
  • 100% TypeScript
  • Supports CJS and ESM
  • Framework agnostic
  • Doesn't allow fields without a name RFC 7578 Section 4.2
  • Fixes an issue where @fastify/busboy becomes unresponsive when processing a field without a value
  • Respects "fieldNameSize" limit that busboy and @fastify/busboy ignore (at least as of 12.06.2023)
  • Introduces 4 new limits:
    • bodySize
    • totalFieldNamesSize
    • totalFieldsSize
    • totalFileSize
  • Stops processing data after bodySize limit is reached (doesn't waste resources). Note: If you choose to use "bodySize" limit, make sure to append a "Connection": "close" header to the response. Aborting an upload and sending a response early in http1, before a request is fully read may cause most browsers to either:
    • Continue uploading payload
    • Hang and keep the connection open indefinitely
    • Show ERR_CONNECTION_RESET page instead of the response body

⚠️ Drawbacks

  • Only supports multipart/form-data
  • Allocates all files to buffers (no streams)

💾 Installation

npm i @xxmichas/bussinboy

npm link

📖 Usage

import { BussinboyErrorMessages, BussinboyEndUserError, BussinboyLimits, bussinboy } from "@xxmichas/bussinboy";

const limits: BussinboyLimits = {
  // ...
};

const errorMessages: BussinboyErrorMessages = {
  // Define your own error messages here, so you can easily return them to the client
  // instead of having to check BussinboyLimitError.code
};

try {
  const data = await bussinboy({ headers, limits, errorMessages }, req);

  const { fields, files } = data;
  console.log(fields, files);

  // ...
} catch (error) {
  let message = "Internal Server Error";
  let status = 500;

  if (error instanceof BussinboyEndUserError) {
    // It's safe to return the error message to the client
    message = error.message;
    status = 413;
  }

  // ...
}

📚 TODO

  • [ ] Add more tests
  • [ ] Add benchmarks