Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / dominictarr/through issues and pull requests
#50 - Reduce the size of the npm package by limiting the included files
Issue -
State: closed - Opened by paazmaya almost 6 years ago
- 1 comment
#49 - end called while paused for Readable Streams
Pull Request -
State: open - Opened by joewagner about 6 years ago
- 3 comments
#48 - Create .npmignore
Pull Request -
State: open - Opened by eugenelim over 6 years ago
#47 - Reorder package.json and add "files" field
Pull Request -
State: open - Opened by dada1134 over 7 years ago
#46 - .unpipe is not a function
Issue -
State: closed - Opened by danielkwinsor over 7 years ago
- 3 comments
#45 - stream must be close properly
Pull Request -
State: closed - Opened by win-t over 7 years ago
- 1 comment
#44 - Whitelist package files
Pull Request -
State: closed - Opened by dguettler about 8 years ago
- 5 comments
#43 - Should keep internal references to globals
Issue -
State: closed - Opened by fatso83 over 8 years ago
- 4 comments
#42 - Add files entry to package.json.
Pull Request -
State: closed - Opened by jamestalmage over 8 years ago
- 1 comment
#41 - Create .npmignore
Pull Request -
State: closed - Opened by southpolesteve over 8 years ago
- 1 comment
#40 - objectMode?
Issue -
State: closed - Opened by tallesl almost 9 years ago
- 1 comment
#39 - Best way to handle an error
Issue -
State: open - Opened by eddieajau almost 9 years ago
- 1 comment
#38 - Added ability to add error handler
Pull Request -
State: closed - Opened by KodeAndGame about 9 years ago
- 1 comment
#37 - events for closing
Issue -
State: open - Opened by shaunc about 9 years ago
- 2 comments
#36 - support node stream callbacks to default write and end
Pull Request -
State: closed - Opened by shaunc about 9 years ago
- 1 comment
#35 - Update package.json
Pull Request -
State: closed - Opened by coliff about 9 years ago
- 2 comments
#34 - Github releases for new versions
Issue -
State: closed - Opened by orlitzky about 9 years ago
- 5 comments
#33 - Source stream leaked then piped
Issue -
State: closed - Opened by CrabDude over 9 years ago
- 5 comments
#32 - Fix non-strict null check
Pull Request -
State: closed - Opened by jarofghosts over 9 years ago
- 2 comments
#31 - Concurrency in this.queue()
Issue -
State: open - Opened by vsukhomlinov over 9 years ago
- 3 comments
#30 - Weird behavior
Issue -
State: closed - Opened by gangstead almost 10 years ago
- 2 comments
#29 - Expected behavior
Issue -
State: open - Opened by fearphage almost 10 years ago
- 1 comment
#28 - swallows errors in browser
Issue -
State: closed - Opened by davidguttman almost 10 years ago
- 7 comments
#27 - how to do asynchronous, secondary reads from files and databases
Issue -
State: open - Opened by loveencounterflow almost 10 years ago
- 2 comments
#26 - 2.3.5 doesn't isn't in the npm registry
Issue -
State: closed - Opened by hojberg about 10 years ago
- 1 comment
#25 - Add upcase example.
Pull Request -
State: closed - Opened by caike about 10 years ago
- 1 comment
#24 - `end` emitted while stream on pause
Issue -
State: closed - Opened by alexbeletsky over 10 years ago
- 4 comments
#23 - Pause doesn't affect write
Issue -
State: open - Opened by azer over 10 years ago
- 5 comments
#22 - Callback with stream
Issue -
State: closed - Opened by rejeep over 10 years ago
- 2 comments
#21 - Consistency with return values
Pull Request -
State: closed - Opened by chrisnojima over 10 years ago
- 4 comments
#20 - through versus Transform in node 0.10+
Issue -
State: open - Opened by jeromew over 10 years ago
- 2 comments
#19 - Real world usages
Issue -
State: closed - Opened by cyrusdavid about 11 years ago
- 1 comment
#18 - Once .end() is called, it can never be called again even if autoDestroy is false.
Issue -
State: open - Opened by cowboy about 11 years ago
- 4 comments
#17 - no 'close' event on node 0.11.2 (ok on 0.11.0, 0.10.x, 0.8.x)
Issue -
State: closed - Opened by isao over 11 years ago
- 9 comments
#16 - no data piped through async streams, stream finishes in wrong order
Issue -
State: closed - Opened by timoxley over 11 years ago
- 6 comments
#15 - this.emit switches into old steam mode on 0.10?
Issue -
State: open - Opened by ghost over 11 years ago
- 1 comment
#14 - mark "write" method as code
Pull Request -
State: closed - Opened by dandv over 11 years ago
- 1 comment
#13 - Fix embarrassing typo on npmjs.org
Issue -
State: closed - Opened by dandv over 11 years ago
- 4 comments
#12 - Test on 0.10 on Travis
Pull Request -
State: closed - Opened by gsf over 11 years ago
- 1 comment
#11 - Pausing internally gets overridden by downstream streams
Issue -
State: open - Opened by ForbesLindesay over 11 years ago
- 6 comments
#10 - Typo fix
Pull Request -
State: closed - Opened by KyleAMathews over 11 years ago
- 1 comment
#9 - latest tape has a small test runner
Issue -
State: open - Opened by defunctzombie over 11 years ago
#8 - testling enabled super cow powers
Pull Request -
State: closed - Opened by defunctzombie over 11 years ago
- 1 comment
#7 - add testling tests for browser compliance
Issue -
State: closed - Opened by defunctzombie over 11 years ago
- 1 comment
#6 - doc
Pull Request -
State: closed - Opened by juliangruber over 11 years ago
- 1 comment
#5 - Alias `queue()` to `push()`
Pull Request -
State: closed - Opened by Raynos over 11 years ago
- 3 comments
#4 - internal buffer should not be exposed
Pull Request -
State: closed - Opened by ralphtheninja almost 12 years ago
#3 - Ensure that end will be queued if paused with data
Pull Request -
State: closed - Opened by jeffbski almost 12 years ago
- 7 comments
#2 - use readable-stream
Pull Request -
State: closed - Opened by Raynos about 12 years ago
- 4 comments
#1 - package.json: s/repo/repository/
Pull Request -
State: closed - Opened by isaacs about 12 years ago