Added Triaged label.

+vsm/blois (you changed pkg/browser/lib/dart.js recently)

Who is the maintainer of this?

cc @blois.
cc @vsmenon.

Not entirely sure that "dart.js" falls under area-dart2js.

Also, it seems rather wierd to me that you would deploy both main.dart.js and main.dart.precompiled.js in a packaged app. Perhaps it would be better to change your build script to overwrite main.dart.js with the CSP version.

This is purely a development scenario.

For a web app, one can 'run as Javascript' and dart.js does the right thing, which is great to quickly validate that dart2js is doing the right thing.

For a packaged app, this does not work at the moment, because dart.js loades the non-CSP-friendly js file.
There are pretty simple tricks one can add to dart.js to allow it to detect inline evaluation. This would make testing the compiled packaged app a lot easier.

If it's a dev-time workaround for chrome apps then it sounds like it should be a separate file rather than being included in boot.js.

Agree with Peter that it seems that the generated main.dart.js should be compiled in the form that app needs it to be executed. I expect CSP to be enabled via an app or server policy, so at compile time the developer should know whether CSP is expected to be on or off.

Removed Area-Dart2JS label.
Added Area-Pkg label.

Added Pkg-Browser label.