connect-busboy
Connect middleware for busboy

connect-busboy downloads connect-busboy version

connect-busboy유사 패키지:
npm 다운로드 트렌드
3 년
🌟 connect-busboy의 README.md에 실시간 사용 차트를 표시하려면 아래 코드를 복사하세요.
## Usage Trend
[![Usage Trend of connect-busboy](https://npm-compare.com/img/npm-trend/THREE_YEARS/connect-busboy.png)](https://npm-compare.com/connect-busboy#timeRange=THREE_YEARS)
Cumulative GitHub Star Trend
🌟 connect-busboy의 README.md에 GitHub Stars 트렌드 차트를 표시하려면 아래 코드를 복사하세요.
## GitHub Stars Trend
[![GitHub Stars Trend of connect-busboy](https://npm-compare.com/img/github-trend/connect-busboy.png)](https://npm-compare.com/connect-busboy)
통계 세부사항
패키지
다운로드
Stars
크기
Issues
발행일
라이선스
connect-busboy28,9991564.57 kB0--
connect-busboy의 README

Description

Connect middleware for busboy.

Requirements

Install

npm install connect-busboy

Example

const busboy = require('connect-busboy');

// Default options, no immediate parsing
app.use(busboy());
// ...
app.use((req, res) => {
  if (req.busboy) {
    req.busboy.on('file', (name, file, info) => {
      // ...
    });
    req.busboy.on('field', (name, value, info) => {
      // ...
    });
    req.pipe(req.busboy);
  }
  // etc ...
});

// Default options, immediately start reading from the request stream and
// parsing
app.use(busboy({ immediate: true }));
// ...
app.use((req, res) => {
  if (req.busboy) {
    req.busboy.on('file', (name, file, info) => {
      // ...
    });
    req.busboy.on('field', (name, value, info) => {
      // ...
    });
  }
  // etc ...
});

// Any valid Busboy options can be passed in also
app.use(busboy({
  highWaterMark: 2 * 1024 * 1024,
  limits: {
    fileSize: 10 * 1024 * 1024,
  }
}));

Troubleshooting

'TypeError: Cannot call method 'on' of undefined'

If you find that req.busboy is not defined in your code when you expect it to be, check that the following conditions are met. If they are not, req.busboy won't be defined:

  1. The request method is not GET or HEAD
  2. The Content-Type header specifies that is "application/x-www-formurlencoded" or starts with "multipart/*"
  3. The Content-Length header is defined or chunked transfer encoding is in use. This criteria should be met by all well-behaved HTTP clients and is unlikely the problem.