Convert 'firstValues' helper into an option for Formidable constructor. #973

Activity

1. GrosSacASac commented on Apr 3, 2024

   

   GrosSacASac

   on Apr 3, 2024

   Contributor

   More actions

   Some people asked in the past to make the library smaller. This would make it bigger.

   Sometimes you want some data to be array for example with <select multiple> but not everything
2. tzwel commented on May 3, 2024

   

   tzwel

   on May 3, 2024

   Last edited by tzwel

   More actions

   The current way of doing this is not only ugly (const { firstValues } = require("formidable/src/helpers/firstValues.js")), but confusing too, as this format is vastly different from what express offers and most node devs use express.
   I don't think anyone would care if the library got a little bit bigger for a quality of life improvement like this, it's also completely backwards compatible as it's just a new option, what are the arguments against this?
   Also it's tedious to always append [0] when reading a field, error prone, and makes destructuring impossible

   👍React with 👍7Reacted by Shaibu Emmanuel, t-fritsch, 余森, Lemuel Flores, Erik Jonsson Thorén, evelinagkougklia and kutovoy

   ❤️React with ❤️1Reacted by GrosSacASacs
3. tunnckoCore commented on Apr 21, 2025

   

   tunnckoCore

   on Apr 21, 2025

   Last edited by tunnckoCore

   Member

   More actions

   @tzwel This would not be a thing with modern standards, and the v4 i'm working on.

   for await (const part of parseMultipart(request, options)) {
     console.log(
       `Part Received: Size=${part.size}` Name=${part.key}, Filename=${part.filename}, Type=${part.contentType}, IsFile=${part.isFile()}`,
     );
     if (part.isFile()) {
       console.log('Magic Bytes (first few):', part.magicBytes);
   
       // Option 1: Stream to a file or process chunks
       // const writer = fs.createWriteStream(`./uploads/${part.filename || 'unknown'}`);
       // await part.stream().pipeTo(new WritableStream({ write(chunk){ writer.write(chunk); }}));
       // console.log(`File ${part.filename} saved.`);
   
       // Option 2: Consume fully into memory (careful with large files)
       try {
         const content = await part.bytes();
         console.log(`File ${part.filename} content length: ${content.size}`);
       } catch (err) {
         console.error(`Error processing file ${part.filename}:`, err);
       }
     } else {
       try {
         const textValue = await part.text();
         console.log(`Field ${part.key} value: ${textValue.slice(0, 100)}...`);
       } catch (err) {
         console.error(`Error processing field ${part.key}:`, err);
       }
     }
   }

   The v4 would also have more guides and tools to help around modern stacks and frameworks like Nextjs, React, and others.
4. tunnckoCore

   added

   Status: AcceptedIt's clear what the subject of the issue is about, and what the resolution should be.It's clear what the subject of the issue is about, and what the resolution should be.

   Status: AvailableNo one has claimed for resolving this issue. Generally applied to bugs and enhancement issues.No one has claimed for resolving this issue. Generally applied to bugs and enhancement issues.

   Area: APIsThings related to external and internal APIsThings related to external and internal APIs

   on Apr 16, 2026