Lazily load the entrypoint.

sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart

Index: sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart
diff --git a/sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart b/sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart
index 8294594a5cb0865b2cb5b96255fd91f3ec68b769..87c3a6987b26c2fba57a6792a8976f77d46c7231 100644
--- a/sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart
+++ b/sdk/lib/_internal/pub/lib/src/command/list_package_dirs.dart
@@ -49,8 +49,11 @@ class ListPackageDirsCommand extends PubCommand {
     packages[entrypoint.root.name] = path.join(entrypoint.root.dir, "lib");
 
     // Include the file(s) which when modified will affect the results. For pub,
-    // that's just the lockfile.
-    output["input_files"] = [entrypoint.lockFilePath];
+    // that's just the pubspec and lockfile.
+    output["input_files"] = [
+      entrypoint.lockFilePath,
+      entrypoint.pubspecPath

[nweiz, 2014/07/16 00:33:29]

This doesn't actually read the pubspec anymore, does it? Seems weird to have the
editor re-run it when the pubspec changes if that won't do anything.

[Bob Nystrom, 2014/07/16 17:33:24]

It does, since we are touching "entrypoint" the root package's pubspec gets
read. I could make that lazy within Entrypoint, but I didn't think it was worth
doing.
Yeah, I guess so. I think in practice it doesn't get touched that often.

+    ];
 
     return Future.wait(futures).then((_) {
       log.json.message(output);