I had a similar idea, to read the columns using tput 'cols' for that matter, but still, the child process, does not have any knowledge of the parent window width, hence it does not quite work, it cannot be used to reliably get the window width, as you can see below.

Looking at the above, the tests should not have passed. Sizes are different.

I am working on a product that distributes node and npm as a dependency for an application, which revealed that the 'term-size' MacOS binary is not signed. As 'term-size' is a dependency of npm (a transitive dependency inside boxen which is inside of update-notifier), it would be good for the distributed binary to be codesigned by the entity that makes the binary.

The current workaround is to codesign it ourselves.

Hi,

Is it possible to get the term-size.exe file signed?
This might already be related to previous ticket

I'm seeing this error when process.env.TERM is undefined and process.stdout.isTTY is undefined.

tput: No value for $TERM and no -T specified

It happens on line 60 when tput cols is executed.

https://github.com/sindresorhus/term-size/blob/92aa07ee3a1cc28360af1c908f8a2ae10b6552bd/index.js#L60

Hey there, this is kind of a follow-up to #22. It works fine for the normal git bash window, however when opening e.g. a less pager in that window, it falls back to the default 80/24 values.
I've debugged it and I think I found a bug, but I'd like your confirmation on this.

STR

1. Comment out the following in the index.js to simulate the pager without having to actually have a pager (line 60 is where we'd like to go):
   
2. Temporarily add the following to the bottom of the index.js to execute the size function upon calling the script

var x = terminalSize();
console.log(x);

3. Execute the index.js in a Git Bash and see that it's not returning the correct window size.
   

Possible Solution

The index.js contains this line:

The 'ignore' is duplicated and when I replace the second one with process.stderr, it's working fine.

Resulting in correct window sizes:

Any opinion on this?

Node.js, or rather V8, is planning native FFI support. This would be much better than spawning binaries.

Just for reference, I can't use node-ffi today as it's a native addon and that comes with too many headaches.

I can't print the output to stdout, because its redirected :-), so I use the exit status.

Tested on Linux with node >= 6.x. Also tried rows. I'd expect this to be ancient unix behaviour shared with OS X.

core/node (master $ u=) % node -p 'require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns'     
174
core/node (master $ u=) % node -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?
174
core/node (master $ u=) % nvm run 13 -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?
174
core/node (master $ u=) % nvm run 12 -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?
174
core/node (master $ u=) % nvm run 10 -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?
174
core/node (master $ u=) % nvm run 8 -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?

174
core/node (master $ u=) % nvm run 6 -p 'process.exit(require("tty").WriteStream(require("fs").openSync("/dev/tty", "w")).columns)' < /dev/null >/dev/null 2>/dev/null; echo $?

174

2.2.0 has a bunch of .DS_Store files in the vendor subdirectory. https://unpkg.com/browse/[email protected]/vendor/

Publishing from a newer npm version should not include them, but in case they are included you can add a .npmignore file in the vendor subdirectory and add .DS_Store

So trying to fix this issue I found that in this line of term-size stops the execution:

const size = execa.sync('resize', ['-u']).stdout.match(/\d+/g);

Reproduce

With the vendor/resize binary, execute a script:

#!/usr/bin/env node
const path = require('path')
const execa = require('execa')
const size = execa.shellSync(path.join(__dirname, 'resize'), ['-u']).stdout.match(/\d+/g)
console.log(size)

And executing like this:

$ ./index.js >log.txt 2>&1 &
[2] 15736
[2]  + 15736 suspended (tty output)  ./index.js > log.txt 2>&1
$ cat log.txt

$ 

This doesn't happen when you don't run the process in the background (so, without the last &):

$ ./index.js >log.txt 2>&1
$ cat log.txt
[ '111', '25' ]
$

This could be an error in execa or in the resize binary, I have no clue.

I'd like to be able to rebuild vendor/resize binary for the debian package. Or can I skip that binary if I only wanted to be able to use term-size from ava.

I have an Apple silicon device and am trying to avoid installing Rosetta and use native versions of applications. When using term-size, I get this error:

/bin/sh: /Users/x/y/node_modules/term-size/vendor/macos/term-size: Bad CPU type in executable

It would be great if term-size were updated to support Apple silicon without requiring Rosetta, either by including an Apple silicon binary or not requiring a binary at all.

Hey there,

could you add support for the Git Bash console (that you get by default when installing on Windows)?
Getting the size has basically been done (I shamelessly stole most of this from here, around line 90)

const {execSync} = require('child_process');
var buf = execSync('tput cols && tput lines', {stdio: ['ignore', 'pipe', process.stderr]});
var sz = buf.toString().trim().split('\n');
if(sz && sz.length == 2){
    return create(sz[0], sz[1]);
}

I can create a PR if you want, however I'm not really a js-dev, so you might want to do this yourself.

Hi,
is it possible to eliminate the exe file inside the package?
https://registry.npmjs.org/term-size/-/term-size-2.1.1.tgz
because of this our organization it security web filtering block access to this module and it causes us a lot of trouble.

not work in windows 10 git bash terminal