Jocelyn Badgley

I've been wrestling with this problem today. I thought I could address it by adding a resolver that uses `enhanced-resolve`, but apparently adding a resolver (which can only be commonjs?)...

I'm also having this struggle, I cannot seem to figure out how to define a named export at all.

Is this still up to date?

Isn't req.param() being removed?

@Fishrock123 right. is it only being deprecated and not removed in 5.0?

Dropping 0.10 for 5.0 sounds good to me. Express 4 isn't that different, right?

Perhaps a better question to ask is, what does Express gain by dropping 0.10 but not 0.12? Most of the improvements you mention cant adopted until 0.12 is abandoned.

Can you clarify what you mean by "use promises"? I was under the impression that just meant accepting a thenable as the return on middleware and routes. That shouldn't require...

Requiring Node 4 would be a pretty huge step up, but as long as Express 4 is still maintained I don't think it's a huge problem. Just need to make...

I agree with @jonathanong, don't set a default. Anything that is a default becomes an included dependency that cannot be opted out of. That's added weight that express doesn't need....