Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please help make it more obvious when pub detects a file collision #15668

Closed
sethladd opened this issue Dec 17, 2013 · 2 comments
Closed

Please help make it more obvious when pub detects a file collision #15668

sethladd opened this issue Dec 17, 2013 · 2 comments
Labels
closed-duplicate Closed in favor of an existing report type-enhancement A request for a change that isn't a bug

Comments

@sethladd
Copy link
Contributor

I'm trying to help the new vanilla Dart of TodoMVC, but when I run pub build, I get this error:

--- Dec 12, 2013 3:57:28 PM Running pub build ... ---
Pub build failed, [65] Building todomvc_dart.....
[Info in Dart2JS]:
Generated todomvc_dart|web/dart/app.dart.js (127618 characters) in 0:00:07.610880
Build error:
Transforms {Dart2JS on todomvc_dart|web/dart/app.dart} all emitted asset todomvc_dart|web/dart/app.dart.js.
Build failed.

A couple of questions:

* Not sure what "all emitted asset" means. Was that an error? That is, is that good or bad? :)

* I think I see one transform in there (Dart2JS) but I also see the word "all".

* I'm not clear what the | means here. Why do we include the name of the project, and not just the path to the file/asset in question?

* No exception is emitted, so not sure how to give you more info. I ran this by right-clicking on pubspec.yaml and selected "pub build"

For the record, no build directory was created.

@nex3
Copy link
Member

nex3 commented Dec 17, 2013

Added Duplicate label.
Marked as being merged into #14593.

@DartBot
Copy link

DartBot commented Jun 5, 2015

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

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

4 participants