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

co-busboy_p

v0.0.1

Published

Promiseify co-busboy

Downloads

1

Readme

co busboy

NPM version build status Test coverage David deps npm download

busboy multipart parser using co or koa.

Example

var parse = require('co-busboy')

app.use(function* (next) {
  // the body isn't multipart, so busboy can't parse it
  if (!this.request.is('multipart/*')) return yield next

  var parts = parse(this)
  var part
  while (part = yield parts) {
    if (part.length) {
      // arrays are busboy fields
      console.log('key: ' + part[0])
      console.log('value: ' + part[1])
    } else {
      // otherwise, it's a stream
      part.pipe(fs.createWriteStream('some file.txt'))
    }
  }
  console.log('and we are done parsing the form!')
})

Note that parts will be delievered in the order they are defined in the form. Put your CSRF token first in the form and your larger files last.

If you want co-busboy to automatically handle the fields, set the autoFields: true option. Now all the parts will be streams and a field object and array will automatically be populated.

var parse = require('co-busboy')

app.use(function* (next) {
  var parts = parse(this, {
    autoFields: true
  })
  var part
  while (part = yield parts) {
    // it's a stream
    part.pipe(fs.createWriteStream('some file.txt'))
  }
  console.log('and we are done parsing the form!')
  // .field holds all the fields in key/value form
  console.log(parts.field._csrf)
  // .fields holds all the fields in [key, value] form
  console.log(parts.fields[0])
})

Example for csrf check

Use options.checkField hook function(name, val, fieldnameTruncated, valTruncated) can handle fields check.

var parse = require('co-busboy')

app.use(function* (next) {
  var ctx = this
  var parts = parse(this, {
    checkField: function (name, value) {
      if (name === '_csrf' && !checkCSRF(ctx, value)) {
        var err =  new Error('invalid csrf token')
        err.status = 400
        return err
      }
    }
  })
  var part
  while (part = yield parts) {
    // ...
  }
})

Example for filename extension check

Use options.checkFile hook function(fieldname, file, filename, encoding, mimetype) can handle filename check.

var parse = require('co-busboy')
var path = require('path')

app.use(function* (next) {
  var ctx = this
  var parts = parse(this, {
    // only allow upload `.jpg` files
    checkFile: function (fieldname, file, filename) {
      if (path.extname(filename) !== '.jpg') {
        var err = new Error('invalid jpg image')
        err.status = 400
        return err
      }
    }
  })
  var part
  while (part = yield parts) {
    // ...
  }
})

API

parts = parse(stream, [options])

var parse = require('co-busboy')
var parts = parse(stream, {
  autoFields: true
})

options are passed to busboy. The only additional option is autoFields.

Note: If busboy events partsLimit, filesLimit, fieldsLimit is emitted, will throw an error.

part = yield parts

Yield the next part. If autoFields: true, this will always be a file stream. Otherwise, it will be a field as an array.

  • Readable Stream

    • fieldname
    • filename
    • transferEncoding or encoding
    • mimeType or mime
  • Field[]

    1. fieldname
    2. value
    3. valueTruncated - Boolean
    4. fieldnameTruncated - Boolean

If falsey, then the parser is done.

parts.field{}

If autoFields: true, this object will be populated with key/value pairs.

parts.fields[]

If autoFields: true, this array will be populated with all fields.

License

The MIT License (MIT)

Copyright (c) 2013 Jonathan Ong [email protected] Copyright (c) 2015 cojs and other contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.