Comments (5)
(This is Node v0.10.5 btw.)
from concat-stream.
Thanks for the bug report. This is a limitation of concat-stream... right now it only knows how to process streams where all chunks are the same type. Here's the current implementation https://github.com/maxogden/node-concat-stream/blob/master/index.js#L32-L41, it keeps an array of chunks and then does some pretty simplistic testing to see which concatenation method it should use.
To add support for multiple types of chunks in a single stream it would add some complexity to the code and could be kind of klunky. Also I'm not sure what the correct should be in your situation (new Buffer('foo') and 'bar'), should it return a Buffer with 'foobar' as the contents or a string 'foobar'?
A quick workaround would be to make sure that you .toString() all buffers before writing them to the stream so that you ensure that all chunks are strings, or vice versa with Buffers
from concat-stream.
Seems like a fair limitation. Some ideas:
- Type-cast to the first type encountered?
- Print a warning if there's a type mismatch?
- Throw an error if there's a type mismatch?
from concat-stream.
imo this is an issue with combined-streams. it should cast all the data to a single type (buffers).
https://github.com/stream-utils/combine-streams handles this
from concat-stream.
Sounds good. I guess we can close this then, yes?
from concat-stream.
Related Issues (20)
- Same functionality as accum? HOT 10
- Publish 1.4.5 to npm
- git tags HOT 2
- Stream empty for concatenated passthrough streams HOT 2
- concat-stream - buffer object in callback is empty. HOT 4
- handling errors HOT 1
- CI HOT 2
- Use standard, error-first callbacks HOT 4
- introduce Readable and Duplex concat streams HOT 1
- Use end-of-stream to determine end
- Convert to real stream HOT 4
- Bump readable-stream version to 2.1.x HOT 1
- Callback never fired if read stream emits an error HOT 2
- Security Vulnerability HOT 2
- Buffer Overhead Vulnerability HOT 2
- Buffer overread vulnerability HOT 2
- Buffer constructor runtime deprecation - this package emits a warning on Node 10
- How big is the difference from 1.6.* to 2.* ? HOT 3
- Is this package still maintained? HOT 1
- Stream consumers: Alternative builtin nodejs solution
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from concat-stream.