Robert Gay

> Are you interested in trying to write a failing test that we see this exclusion, then see if we can fix the test by consulting the exclusion in the...

The commit referenced above as the repro commit was also before the my classifier stuff merged, so it probably wasn't that (though I don't claim it's perfect :) ) FWIW,...

My proposal in #130 definitely won't work for all cases, since I'm pretty sure it (combined with yaml map) won't allow you to have an artifact both with and without...

Getting around to poking around a little bit. The syntax is kinda weird to _combine_ classifiers and/or packaging with the `modules` key, although it's not ambiguous: ``` dependencies: com.github.jnr: "jffi:jar:native":...

It's allowed, but not super common I don't think. The case I can think of at Redfin is (at least internally), we have dependencies on different outputs from the same...

I'd been meaning to circle back around on this. I was holding off doubling down on adding tests, etc. until we had consensus around which approach was favored. Sounds like...

FWIW, at Redfin we had an issue with the default `windowBits` setting for the `compression` module that affected our ability to stream in staging and production environments. Even though we...

I'm in favor of whatever works. :) (Not super familiar with how the site is structured yet.)

I think I'm in favor of this proposal. It makes sense to me to let react-server users ship ES6/esnext directly to browsers that support it. I haven't thought deeply about...

> If I use ES6 in my project and React Server uses ES7, Babel will transform all of code to whatever the transform target is. In this scenario, I was...