Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

weird type error crash #104

Closed
edef1c opened this issue Apr 6, 2015 · 3 comments

Comments

@edef1c
Copy link

commented Apr 6, 2015

buffer.js:84
    throw new TypeError('must start with number, buffer, array or string');
          ^
TypeError: must start with number, buffer, array or string
    at fromObject (buffer.js:84:11)
    at new Buffer (buffer.js:52:3)
    at /home/nathan/src/github.com/then/promise/node_modules/standard/node_modules/string-to-stream/index.js:19:17
    at process._tickCallback (node.js:361:13)
@edef1c

This comment has been minimized.

Copy link
Author

commented Apr 6, 2015

specifically, this is due to StringStream(undefined) being called

    at StringStream (/home/nathan/src/github.com/then/promise/node_modules/standard/node_modules/string-to-stream/index.js:9:47)
    at spawn (/home/nathan/src/github.com/then/promise/node_modules/standard/index.js:182:7)
    at Array.auto.eslint (/home/nathan/src/github.com/then/promise/node_modules/standard/index.js:155:9)
    at module.exports.keys.forEach.listener (/home/nathan/src/github.com/then/promise/node_modules/standard/node_modules/run-auto/index.js:95:32)
    at /home/nathan/src/github.com/then/promise/node_modules/standard/node_modules/run-auto/index.js:43:7
    at Array.forEach (native)
    at Immediate.taskComplete (/home/nathan/src/github.com/then/promise/node_modules/standard/node_modules/run-auto/index.js:42:24)
@edef1c

This comment has been minimized.

Copy link
Author

commented Apr 6, 2015

welp, seems I just need to upgrade

@edef1c edef1c closed this Apr 6, 2015

@feross

This comment has been minimized.

Copy link
Member

commented Apr 6, 2015

Nice - glad you figured it out! 👍

@lock lock bot locked as resolved and limited conversation to collaborators May 11, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.