Eventually, try.dartlang.org should be able to import all packages published on pub.dartlang.org.

I don't know if malicious code is really a problem, or if it is something that should be addressed in a more fundamental level for try.dartlang.org.

If we were to have just a snapshot of a few packages, here's a short list, compiled by looking in the pkg directory for things that look like they might plausibly work in try.dartlang.org and getting their dependencies. So, e.g. args doesn't seem that important, but it ought to work, unittest looks for it, and unittest seems useful. Analyzer seems large and less likely to be used in small snippets, but it might be and Intl requires it, though not for anything that you'd be able to do in try.dartlang.org.

  analyzer
  args
  collection
  crypto
  http
  http_parser
  intl
  logging
  markdown
  matcher
  math
  meta
  path
  serialization
  stack_trace
  string_scanner
  unittest
  yaml

App Engine is a bit annoying, but I've been able to upload packages (and then some).

You can now use the above packages at http://incr.try-dart-lang.appspot.com/.

Added Started label.

Set owner to @peter-ahe-google.

Nice, thanks! It does emphasize the need to make the compile time just be proportional to the change, but it's still great to be able to do something with packages.

I've updated http://incr.try-dart-lang.appspot.com/ to also reuse package libraries. Let me know if that improves the compile times?

BTW: I don't have a meta package. Is that still relevant?

Compile time much better now, 3 or 4 seconds for a trivial program using Intl.

No, meta is not relevant. I don't even know where that came from.