Felix Boehm

@thewilkybarkid I haven't made up my mind if I want to have this in the module or not. Curious if the parser providing this directly would be a value-add for...

It would be amazing to have equivalents to npm's [`--workspace` and `--workspaces` flags](https://docs.npmjs.com/cli/v7/using-npm/workspaces#running-commands-in-the-context-of-workspaces) for `np`.

That's the nice thing when you've got a rendered page: You may simply remove everything that isn't visible (for jQuery users: `$(":not(:visible)").remove()`). I can't tell by looking at the markup...

This would solve this particular problem, but would raise others: Just think about image galeries. And I've seen websites that wrapped their content in `` tags, with image tags at...

Okay, first, you should use a label for this code. The boolean isn't needed and complicates everything. Besides, you remove all nodes that aren't ``s, which isn't such a good...

The problem is that banner ads often are big images inside an `a` tag. I was really annoyed by the number of banner ads I got, so I added this...

In case anyone is interested: I started working on this at [fb55/binary-serializer](https://github.com/fb55/binary-serializer).

The sledge hammer approach taken by [nodejitsu/require-analyzer](https://github.com/nodejitsu/require-analyzer) is to first check if all `requires` can be resolved statically, and if they can't, fire up a new node instance, monkey-patch `Module#require`...

This works as expected, but should be documented. Thanks for raising the issue!

Follow-up on #640. Turns out I didn't have to do this manually after all.