Andrew Goode

Yeah, sounds like it would be best to allow the CLI author to tell sywac one (or more) of the following: 1. This is the error type(s) I'm going to...

For most of my non-command CLIs, I try to organize my package into two main parts - one is a library module intended to be used via `require()`, where most...

Yeah, that makes sense. Using in-process tests gives you a higher degree of flexibility and control over the testing environment (e.g. injection), so I would prefer to use that (instead...

Concerning your last comment about defining a `StacklessError`: That's an interesting approach, but I wouldn't recommend that developers override basic Error semantics (e.g. throwing away the `stack` and `name`) just...

@Arkni Cool, thanks for the reference! Found similar "rebase and merge --ff-only" strategy [here](https://github.com/kahmali/meteor-restivus/issues/89#issuecomment-117805045) via [this SO answer](http://stackoverflow.com/a/29958324/1174467), which can either preserve original commits or squash them before merging. Also...

https://github.com/blog/2141-squash-your-commits @sindresorhus Does this mean you _might_ be tempted to use the green button now? :smiley:

Looks like this is still an issue? I recently upgraded to v7 and today I see that 4.3.3 is the latest: ```console $ npm info restify dist-tags { latest: '4.3.3',...

@hekike I concur, `latest` now points to 7.1.0. I assume someone with write access for this package on the registry did something like `npm dist-tag add [email protected] latest` since my...

From what I can tell, [`unleash`](https://github.com/Netflix/unleash) does not support a `--tag ` argument, so if the team is [using it for releases](https://github.com/restify/node-restify/blob/dc7336bf7b5e89150def2eeb1062d16ff26186a9/CONTRIBUTING.md#cutting-a-release), we may need to open an issue there...

@trentm Awesome, thank you for the update!