![]() Definitely NOT a great or long-term solution. highWaterMark - integer - highWaterMark to use for the parser stream. Valid config properties: headers - object - These are the HTTP headers of the incoming request, which are used by individual parsers. I proceeded to npm run build and firebase deploy -only hosting and it worked just fine. busboy exports a single function: ( function)(< object >config) - Creates and returns a new Writable form parser stream.So I decided to once again uninstall firebase tools ( npm uninstall -g firebase-tools) and then reinstall the previous version ( npm install -g and that's it (did NOT run npm audit fix). We just need to upgrade the firebase tools to fix this issue. ![]() Having no other solutions on the table, I decided to uninstall firebase tools ( npm uninstall -g firebase-tools) and then reinstall the previous version ( npm install -g after first time I did this, I ran npm audit fix (not npm audit fix -force) and all I got a ton of high severity warnings and problems. I came across this issue with busboy package today and it cost me 2hrs to fix this issue. ![]() The additional packages http-status-codes contains. It’s easy to setup busboy and start reading the incoming request. The core multipart/form-data implementation has been extracted to a separate dicer module. Instead of storing intermediate files, it provides a stream to the incoming file. After doing this, I began experiencing the problem detailed in my comment on GitHub. On the server side, we will use busboy npm package to actually do the stream of the uploaded content. Busboy is an event-based streaming parser that’s not tied to Express.js. This is a duplicate of my post on the same issue, on GitHubĪfter deploying my Vuejs3 app a week ago to Firebase, I was prompted to upgrade to the newest version of Firebase Tools (11.0.1) via npm. You can also install v1.4.4-lts.1, it seems to fix the vulnerability met here. Share Improve this answer Follow answered at 12:13 Mojtaba Soleimani 81 1 3 Version 1.4.5 has some bugs which might affect you. I am a novice and this is not advice on what you should do - I'm just relaying what I did and what the outcome was. you can update multer to 1.4.5 as the latest version with npm i multerlatest that uses busboy1.0.0 without any vulnerabilities.
0 Comments
Leave a Reply. |