This comment was originally written by david.elba...@gmail.com

It doesn't work better with r26618.

Added Area-Polymer, Triaged labels.

I tried loading this built and 'pub deploy'ed' version with Chrome, and it worked. Not sure you can access the deployed app with Dartium.

Regardless, we can make deploying a polymer.dart app a lot nicer. There's lots of dart2js hints and warning that are emitted when you run pub deploy on a polymer.dart app.

Luckily, we have top developers working on making this nicer. :)

This comment was originally written by david.elbaz...@gmail.com

Hum.. Very strange.. Even in Chrome it doesn't work and I have the same error in the Console !

there might be some small detail we are doing differently. David/Seth, can you both past here what does your build.dart look like?

This comment was originally written by david.elbaze.9...@gmail.com

Here my code :

import 'package:polymer/component_build.dart';
import 'dart:io';

main() {
  var args = new Options().arguments;
  args.addAll(['--', '--deploy']); // Note: the --deploy is what makes this work
  build(args, ['web/index.html']);
}

Thanks!

mm... still not sure. I'm going to ask you more questions to see if we can figure out what's wrong.

It seems that your code layout is different than the one in Seth's example, but it might be the more common layout. Most applications typically have this layout:

|- web/
| |- index.html
| '- ... more html and .dart files
|
' build.dart

What does your tree look like? (or if you have the code available somewhere, feel free to include the link here and we can take a closer look).

With the above layout, calling build.dart (with the --deploy option) should generate an out folder under 'web/out' that has the code you can use for deployment. Is the code being generated there?

This comment was originally written by david.elba...@gmail.com

Yeah, I forget to tell it...

My tree :
deploy_to_javascript
|
| -packages
| -pubspec.lock
| -pubspec.yaml
| -deploy
| -web
| | -out
| | -index.html
| | -my_element.dart
| | -my_element.html
| -build.dart

I have code in the out/ directory, this code work fine in dartium.

Ok - so the code under web/out/ works, that's great! That's currently what polymer supports.

I've not tried using 'pub deploy' with the app generated in out/, is that what's failing for you? If so, you might have to compile the application by hand with dart2js (the main entrypoint will be web/out/index.html_bootstrap.dart) and ship your html and .js file for now.

The good news is that I'm actively working on making this better. I'm switching our compiler so we can integrate it directly with 'pub deploy' (see issue #12511).

This comment was originally written by david.elbaze....@gmail.com

Yep. When I do the pub deploy, it generate code, i have no error. But when i lauch the application in Chrome or Dartium, i have the error.

I'll try to compile by hand in few minutes, i'll tell you if it fail or not.

PS : I love your job and what you do, it's very interesting. (I'm a student in software engineering)

This comment was originally written by david.elba...@gmail.com

I didn't sucess to compile & execute my deployed / dart2jsED code in Chrome or Dartium :/

This comment was originally written by david.elba...@gmail.com

Hum. It work when I compile with dart2js manually dart files that are in web/out/ :)

Moving to pub, as per Bob's suggestion.

Removed Area-Polymer label.
Added Area-Pub label.

Bumping to high, as I suspect we'll get this done for 1.0

Removed Priority-Unassigned label.
Added Priority-High label.

Added this to the M8 milestone.

FYI - Update on polymer's perspective, we switched over the entire build process to use barback transformers. I hope that once pub-build is implemented this will "just work (tm)" =)

Marked this as blocking #13959.

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