I want the fastest builds, so I'd like to say which files I want compiled.

If you got the fastest builds some other (for purposes of discussion magical) way, would you still care to control which files are compiled? Can you frame this bug in terms of the problem you're running into?

Added this to the Later milestone.

Sure, performance aside. (although, that's a big part of this. compiling to JS is non trivial)

Let's say I have App A, but experiment E. E might be busted, only works in Dartium, won't be deployed, just for me. I don't want to slow down the build, introduce extraneous error messages or warnings, or break the build if all I care about is App A.

So I guess this is about cycle times mostly, and reducing warnings/output about broken builds that I know are broken.

Issue #15255 has been merged into this issue.

Removed Priority-Unassigned label.
Added Priority-Medium label.

Removed Priority-Medium label.
Added Priority-High label.

Marked this as blocking #15829.

I believe the current plan for issue #14673 will cover this use case. As such, can we close out this bug?

We now let you specify which directory you want to build, but not which entrypoints.

This ticket is a bit vague. If you specify some entrypoint, presumably you do also want all of the other assets needed by that entrypoint. Is it more that you want to exclude certain entrypoints from being compiled using dart2js?

Sure, excluding entry points would help. See https://code.google.com/p/dart/issues/detail?id=14594#c2 In that case, I wanted to say "don't build this thing, it's busted and I know it"

OK, retargeting the bug.

Changed the title to: "Allow excluding entrypoints from the dart2js transformer".

I'm gonna start poking at this. My plan is to add support for $exclude and $include to transformers in general, and then we'll get dart2js for free.

cc @nex3.
Set owner to @munificent.
Added Started label.

$include and $exclude are in.

Added Fixed label.

thanks!

We might want to document this. CC'ing Sharon.

cc @Sfshaza.

Yup: https://code.google.com/p/dart/issues/detail?id=17128

This issue has been moved to dart-lang/pub#691.