For "nip", I suspect that is because it quite literally is "plumbing" of a sort that people have their favourite tools for from before, whether it's awk, sed, perl, or any other language interpreter that can easily take an expression on the command line (e.g. ruby can pretend to be both awk and sed of sorts with the right command line options).
It looks neat, but it'd appeal to people who spend most of their time doing stuff with node anyway, and doesn't have other scripting alternatives they prefer for one-liners.
There's a ton of inertia for those kind of tools. E.g. even though I prefer Ruby, I tend to use awk for one-liners because I can expect it to be available "everywhere", and because I have "muscle memory" for dozens of common patterns because I started using it so long ago.
That's not a criticism of your tool - just some thoughts on reasons why it might be harder to get attention for that kind of tool.
It looks neat, but it'd appeal to people who spend most of their time doing stuff with node anyway, and doesn't have other scripting alternatives they prefer for one-liners.
There's a ton of inertia for those kind of tools. E.g. even though I prefer Ruby, I tend to use awk for one-liners because I can expect it to be available "everywhere", and because I have "muscle memory" for dozens of common patterns because I started using it so long ago.
That's not a criticism of your tool - just some thoughts on reasons why it might be harder to get attention for that kind of tool.