strip-bom-stream
Advanced tools
Strip UTF-8 byte order mark (BOM) from a stream
From Wikipedia:
The Unicode Standard permits the BOM in UTF-8, but does not require nor recommend its use. Byte order has no meaning in UTF-8.
$ npm install strip-bom-stream
import fs from 'node:fs';
import stripBomStream from 'strip-bom-stream';
fs.createReadStream('unicorn.txt')
.pipe(stripBomStream())
.pipe(fs.createWriteStream('unicorn.txt'));
It's a Transform stream.
The strip-bom package is used to remove BOM from strings and buffers. Unlike strip-bom-stream, which works with streams, strip-bom is more suited for handling individual strings or buffers. It is useful when you need to process text data that is already loaded into memory.
The remove-bom-stream package is another alternative for removing BOM from streams. It functions similarly to strip-bom-stream but may have different performance characteristics or additional features. It is a good alternative if you are looking for similar functionality.
FAQs
Strip UTF-8 byte order mark (BOM) from a stream
The npm package strip-bom-stream receives a total of 1,588,143 weekly downloads. As such, strip-bom-stream popularity was classified as popular.
We found that strip-bom-stream 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
Five malicious NuGet packages impersonate Chinese .NET libraries to deploy a stealer targeting browser credentials, crypto wallets, SSH keys, and local files.
Security News
pnpm 11 turns on a 1-day Minimum Release Age and blocks exotic subdeps by default, adding safeguards against fast-moving supply chain attacks.
Security News
The remediated findings include organization permission bugs, stale project access after transfers, OIDC replay edge cases, audit logging gaps, and an IDOR in API token deletion.