It's possible this should work somewhat differently for "pub serve" than for "pub build". For building the primary use-case for building a specific directory is to take the output -- for example, an example app -- and put it on a server somewhere. This means that saying e.g. "pub build example/foo" makes a lot of sense. For "pub serve", though, it may be more useful to just have the server always make the examples and tests accessible. You'd still run "pub serve" without any arguments, but then you could go to "http://localhost/_pkg/example/foo" (or something, "_pkg" is just a strawman).

Marked this as blocking #15859.

Unmarked this as blocking #15859.

Marked this as blocking #15830.

Added DevStory label.

Set owner to @nex3.
Added Started label.

Marked this as blocking #16889.

Support for this has been added in r32818. "pub serve" can now serve files from multiple directories, each on a different port. By default it serves "web" on port 8080 and "test" on port 8081; additional command-line arguments can be passed to cause it to serve other directories. For example, "pub serve example/foo" will serve example/foo on port 8082 (8080 and 8081 are always reserved for "web" and "test").

Added Fixed label.

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