Some web servers have a limit on the number of chunks, and you can set minChunkSize to ensure the size of chunk sent to the server.
var fs = require('fs');var FormStream = require('formstream');var filepath = './big-file.zip';fs.stat(filepath, function (err, stat) { new FormStream({ // send >= 2MB chunk buffer size to the server minChunkSize: 1024 * 1024 * 2, }).field('status', 'share file') .field('access_token', 'your access token') .file('file', filepath, 'big-file.zip', stat.size) .pipe(process.stdout); // your request stream});
API Doc
Field names and filenames use percent encoding for carriage returns (%0D),
line feeds (%0A), and double quotes (%22) in multipart headers.
Other characters and field contents remain unchanged.
The field(), buffer(), and stream() methods throw a TypeError synchronously
if a supplied MIME type contains a carriage return or line feed.
formstream([options])
Create a form instance.
Arguments
options.minChunkSize Number - min chunk size to emit data event
Returns
Form - form instance
FormStream#field(name, value[, mimeType])
Add a normal field to the form.
Arguments
name String - Name of field
value String - Value of field
mimeType String - Optional. Content-Type of the field
Maintainers prepare releases through a pull request that updates the version in
package.json and describes the changes in CHANGELOG.md. To update the version
without creating a commit or tag, run npm version patch --no-git-tag-version
(or use minor, major, or an explicit version).
After the PR merges into master, release.yml compares the package versions
before and after the push. It publishes only when the version changes. The
workflow skips versions already on npm, runs the project checks, and publishes
with npm trusted publishing and provenance. Stable versions use the latest
dist-tag; prerelease versions use next.
After npm publishing succeeds, the workflow creates a GitHub release with a
v<version> tag at the commit that triggered the workflow and automatically
generated release notes. Prerelease versions are marked as GitHub prereleases.
To retry a failed release, rerun the failed workflow in GitHub Actions. If the
version is already on npm, the workflow still creates the missing GitHub release.
Existing GitHub releases remain unchanged.
Configure the formstream package's trusted publisher on npm with these values:
Provider: GitHub Actions
Organization: node-modules
Repository: formstream
Workflow filename: release.yml
Environment: leave empty
Allow direct publishing with npm publish
The workflow uses OIDC and does not require an NPM_TOKEN or GIT_TOKEN secret.
See the npm trusted publishing documentation
for package configuration instructions.