Tony Valderrama

@woodyrew is this still open for submissions? Happy to push out a quick PR that enables file pattern matching, as well as the option to preserve original extensions.

Riffing on the above suggestion, I've had several occasions where it made sense to write a builder or currying wrapper in order to leverage inference of complex, hard-to-specify types. `auto`...

I second this request, both to manage package size and also to suppress misbehaving optional packages. **The Problem** To elaborate, a package we rely on (`good-package`) has an optional dependency...

Also, could we edit the title for clarity: `Add way to ignore individual optional packages`?

If a non-optional package were suppressed, that would presumably break all packages which directly or transitively depend on it, including the top-level package. It would be great if you can...

That's far more complicated, then. I'll split off a separate feature request if that's the kind of scenario you want to support with this issue. /shrug

> if I only use part of them, then some required dependencies can suppressed Definitely a reasonable use case that I have encountered. We also use `rollup` in the build...