
Research
Security News
The Landscape of Malicious Open Source Packages: 2025 Mid‑Year Threat Report
A look at the top trends in how threat actors are weaponizing open source packages to deliver malware and persist across the software supply chain.
next-multipart
Advanced tools
Next-multipart is a small utility library to ease the process of file uploads with Next.js. It uses [formidable](https://github.com/node-formidable/formidable) under the hood, but with much less work to do and a modern API
Next-multipart is a small utility library to ease the process of file uploads with Next.js. It uses formidable under the hood, but with much less work to do and a modern API
Installation is pretty straight forward. Simply run one of the following commands to install it to your Next.js app.
yarn add next-multipart
npm i next-multipart
pnpm add next-multipart
TL;DR:
import { withFileUpload, getConfig } from 'next-multipart'
withFileUpload
export const config = getConfig()
req.file
(if the request contained one file field) or req.files
await req.file.toBuffer()
to load the file into the memoryThe withFileUpload
function is a higher-order function which should be wrapped around
an api route from next.js:
import { withFileUpload } from 'next-multipart';
export default withFileUpload(async (req, res) => {
res.json({test: 1})
})
By default it will attach the files and files which were posted to that endpoint to the NextApiRequest
(in this case req
) if the method was POST
, PATCH
or PUT
and the Content-Type
header was set to multipart/form-data
.
If the request includes files they will be saved to the disk in the os.tmpdir()
directory.
After the execution of the handler all files will be cleaned up automatically.
The following properties are added to the Request:
files
: Array of EnhancedFilefile
: Single EnhancedFile. Will be undefined
if there are no filesfields
: Object containing the name of the field as the key and the value of the field as the valueYou can also pass a second parameter options
to withFileUpload
. Options is an object with the following values:
// Methods which should be allowed. Defaults to ['POST', 'PATCH', 'PUT']
allowedMethods?: HTTP_METHOD[];
// Flag whether the files should be removed after the execution of the handler. Defaults to true. You will probably not need to touch this.
cleanupFiles?: boolean;
// Options to change the behavior of formidable (e.g. max file size). Please refer to the https://github.com/node-formidable/formidable#options
formidableOptions?: formidable.Options
Basically just formidable.File but with two added helper functions:
// Loads the file asynchronously from the file system and loads it into the memory
// will throw if the file doesn't exists anymore
toBuffer: () => Promise<Buffer>
// Deletes the file from the file system if it exists
destroy: () => Promise<void>
FAQs
Next-multipart is a small utility library to ease the process of file uploads with Next.js. It uses [formidable](https://github.com/node-formidable/formidable) under the hood, but with much less work to do and a modern API
The npm package next-multipart receives a total of 28 weekly downloads. As such, next-multipart popularity was classified as not popular.
We found that next-multipart demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A look at the top trends in how threat actors are weaponizing open source packages to deliver malware and persist across the software supply chain.
Security News
ESLint now supports HTML linting with 48 new rules, expanding its language plugin system to cover more of the modern web development stack.
Security News
CISA is discontinuing official RSS support for KEV and cybersecurity alerts, shifting updates to email and social media, disrupting automation workflows.