feross/chrome-net issues and pull requests

#46 - fix: modernise code

Pull Request - State: open - Opened by ThaUnknown 12 months ago

#45 - F

Issue - State: closed - Opened by Endlessnonsense over 3 years ago

#44 - Dose this still work?

Issue - State: open - Opened by jimmywarting over 3 years ago - 1 comment

#43 - Use object shorthand for properties

Pull Request - State: closed - Opened by LinusU over 4 years ago

#42 - Update tape to the latest version 🚀

Pull Request - State: closed - Opened by greenkeeper[bot] over 4 years ago
Labels: greenkeeper

#41 - An in-range update of browserify is breaking the build 🚨

Issue - State: closed - Opened by greenkeeper[bot] over 5 years ago - 2 comments
Labels: greenkeeper

#40 - Update dependencies to enable Greenkeeper 🌴

Pull Request - State: closed - Opened by greenkeeper[bot] over 5 years ago - 1 comment
Labels: greenkeeper

#39 - Action required: Greenkeeper could not be activated 🚨

Issue - State: closed - Opened by greenkeeper[bot] over 5 years ago
Labels: greenkeeper

#38 - 3.3.2

Pull Request - State: closed - Opened by lidel over 5 years ago

#37 - Fix test failures

Pull Request - State: closed - Opened by jscissr over 5 years ago - 1 comment

#36 - Improved feature-detection of chrome.sockets

Pull Request - State: closed - Opened by lidel over 5 years ago - 7 comments

#35 - Action required: Greenkeeper could not be activated 🚨

Issue - State: closed - Opened by greenkeeper[bot] over 6 years ago
Labels: greenkeeper

#34 - destroy callback not getting called

Pull Request - State: closed - Opened by luke about 7 years ago - 1 comment

#33 - Connect socket via proxy

Issue - State: closed - Opened by poojas2288 over 7 years ago - 1 comment

#32 - standard

Pull Request - State: closed - Opened by feross over 7 years ago

#31 - Don't increment bytesRead or unrefTimers if socket is paused

Pull Request - State: closed - Opened by mcelrath over 7 years ago - 9 comments

#30 - Error in response to sockets.tcp.getInfo: TypeError: this.isPaused is not a function

Issue - State: closed - Opened by stevenmason about 8 years ago - 1 comment

#29 - added require Buffer

Pull Request - State: closed - Opened by MikeKovarik over 8 years ago - 1 comment

#28 - Thorough check for Chrome App enviroment

Pull Request - State: closed - Opened by MikeKovarik over 8 years ago - 2 comments

#27 - this.isPaused is not a function

Issue - State: closed - Opened by MikeKovarik over 8 years ago - 3 comments

#26 - Add me as npm owner

Issue - State: closed - Opened by jscissr almost 9 years ago - 2 comments

#25 - 3.0.0 Seems to break the simple http server

Issue - State: closed - Opened by No9 over 9 years ago - 8 comments

#24 - Merge in jscissr/net-chrome-apps

Pull Request - State: closed - Opened by jscissr over 9 years ago - 1 comment

#23 - Connect after listeners

Pull Request - State: closed - Opened by throughnothing almost 10 years ago - 3 comments

#22 - Fix Socket().connect() API when used directly

Pull Request - State: closed - Opened by throughnothing almost 10 years ago

#21 - sending buffer slice bugfix + unittest

Pull Request - State: closed - Opened by mrk-its almost 10 years ago - 1 comment

#20 - `server.address()` returns `{port: 0, ...}` while server is listening on random port.

Issue - State: closed - Opened by hackwaly almost 10 years ago - 1 comment

#19 - Tests currently hang on "TCP listen works (echo test)"

Issue - State: closed - Opened by feross almost 10 years ago - 5 comments

#18 - launch custom chrome path in tests. launch and load absolute path

Pull Request - State: closed - Opened by soldair almost 10 years ago - 2 comments

#17 - net.Socket is not supported

Issue - State: closed - Opened by carlosjeurissen almost 10 years ago - 2 comments

#16 - Add in optimization

Pull Request - State: closed - Opened by Janpot about 10 years ago - 2 comments

#15 - match chrome errors to node errors

Issue - State: closed - Opened by marmolejo about 10 years ago - 2 comments

#14 - Chrome-net on android

Issue - State: closed - Opened by zoutepopcorn about 10 years ago - 2 comments

#13 - fix calling destroy() before create callback

Pull Request - State: closed - Opened by marmolejo about 10 years ago - 1 comment

#12 - Chrome complains about unchecked error

Pull Request - State: closed - Opened by marmolejo about 10 years ago - 1 comment

#11 - remove complains when connection is already closed

Pull Request - State: closed - Opened by marmolejo about 10 years ago - 1 comment

#10 - chrome-http?

Issue - State: closed - Opened by beriberikix over 10 years ago - 3 comments

#9 - Socket.prototype.destroySoon

Issue - State: closed - Opened by perceptron8 over 10 years ago - 8 comments

#8 - Socket.prototype._resetTimeout

Issue - State: closed - Opened by perceptron8 over 10 years ago - 4 comments

#7 - Should `decodeStrings` writable stream option be set?

Issue - State: closed - Opened by feross over 10 years ago
Labels: question

#6 - Add test: when one side terminates the connection, stream ends correctly

Issue - State: closed - Opened by feross over 10 years ago

#5 - Use new chrome.sockets.* APIs

Issue - State: closed - Opened by feross over 10 years ago - 2 comments
Labels: enhancement

#4 - Could not load extension from ''. Manifest file is missing or unreadable.

Issue - State: closed - Opened by dzlab almost 11 years ago - 1 comment

#2 - running tests with chromium on linux

Pull Request - State: closed - Opened by dzlab almost 11 years ago - 1 comment

#1 - Need a node streams implementation that uses bops

Issue - State: closed - Opened by feross about 11 years ago - 1 comment

GitHub / feross/chrome-net issues and pull requests