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

#<WriteStream> has no method 'getWindowSize' #36

Closed
deedubs opened this issue Nov 15, 2011 · 6 comments
Closed

#<WriteStream> has no method 'getWindowSize' #36

deedubs opened this issue Nov 15, 2011 · 6 comments
Labels
type: bug a defect, confirmed by a maintainer

Comments

@deedubs
Copy link

deedubs commented Nov 15, 2011

Hank:admin deedubs$ ./node_modules/.bin/mocha

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: Object # has no method 'getWindowSize'
at Object. (/Users/deedubs/Projects/admin/node_modules/mocha/lib/reporters/base.js:68:22)
at Module._compile (module.js:411:26)
at Object..js (module.js:417:10)
at Module.load (module.js:343:31)
at Function._load (module.js:302:12)
at require (module.js:355:19)
at Object. (/Users/deedubs/Projects/admin/node_modules/mocha/lib/reporters/index.js:2:16)
at Module._compile (module.js:411:26)
at Object..js (module.js:417:10)
at Module.load (module.js:343:31)
Hank:admin deedubs$ node -v
v0.4.12

@tj
Copy link
Contributor

tj commented Nov 15, 2011

oh right forgot about 0.4.x haha. To be honest I dont think we should even bother with 0.4.x since 0.6.x is out now

@deedubs
Copy link
Author

deedubs commented Nov 15, 2011

Alright. Didn't know your plans for 0.4.x. Saw it in the package.json so I thought it was going to be supported.

Would you accept a pull to fix this?

@tj
Copy link
Contributor

tj commented Nov 15, 2011

yeah sure it would be a tiny one anyway, just gotta add back the old tty.getWindowSize()

@c4milo
Copy link

c4milo commented Nov 15, 2011

@visionmedia are you guys using 0.6.1 already at LearnBoost?

@c4milo
Copy link

c4milo commented Nov 15, 2011

I'm still hesitant to migrate to 0.6.1, I think it's too soon.

@tj
Copy link
Contributor

tj commented Nov 15, 2011

not yet nope, but it's inevitable so we kinda might as well skip it (or at least not put a lot of effort) for 0.4.x support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug a defect, confirmed by a maintainer
Projects
None yet
Development

No branches or pull requests

3 participants