Reece Daniels

https://github.com/heroku/heroku-accounts/pull/38

Really? I did the following: - heroku accounts:add my_name - prompted for email - prompted for password (used API key) Worked. I'm just using a standard personal login, go to...

@jrochkind - the fact I raised [this](https://github.com/heroku/heroku-accounts/pull/38/files) in Dec last year and it's had 0 comments would support that theory, though I'm still using this fine with multiple accounts locally....

FYI I'm running `ts-prune` as a `pre-push` hook without anything being required of this repo. I presume the same pattern could be applied to `pre-commit`... I have `npm run ts-prune`...

Fair enough. I haven't come across this before. I presume the `pre-commit cli` refers to this: https://pre-commit.com ?

I managed to get it working... The lack of visibility was based on piping logic applied e.g. `ts-prune | grep -v....` PR with code here: https://github.com/nadeesha/ts-prune/pull/180 Piping reference here: https://stackoverflow.com/a/48649918/10732370

Gentle nudge on this @nadeesha - PR is ready if you'd like to give your opinion?

#180 was merged but I can't see that it's been published to npm

@nadeesha looks like this hasn't made it to `npm`. Could you publish?

@Steveb-p did you find a solution to this? I'm also seeing issues with `.down()`. I run mine at the end of an entire mocha test suite, on Node `14.18.2`. My...