tools: Error in polymer build with the last release (v0.11.0)

Hey everyone, taking a look now.

Okay, I think I was finally able to find and fix the issue. I’ll go into more detail in the PR, but the tl;dr was that the code is currently making incorrect assumptions about Node’s ability to convert between Windows, Posix, and URL paths. This was causing polymer-cli to search for bad paths, like src/bower_components/polymer/polymer.html that @Tecm0 spotted.

PR incoming, and thanks again for your patience everyone while we tracked this down.

@abdonrd great! I’d love for us to get https://github.com/yeoman/update-notifier integrated into the CLI, so that these kinds of outdated issues are easier to spot.

Going back to the assumption that this is a Windows-only issue unless anyone else can reproduce.

@FredKSchott wow! 😮 Thanks! Now it works! I thought I had to have absolute paths in the src directory. Maybe it would be nice to document it.

huh, that’s so strange… Lets chalk it up to npm weirdness and move on unless other users report it as well. Thanks for investigating!

@JGSolutions I think your issue is separate from what most people are running into here. Can you create a separate issue with --verbose output included, as well as steps to reproduce from a blank directory?

If anyone else is able to reproduce the no resolver found for ... build bug on Mac, please comment here. Otherwise, I’m going to assume this is a Windows issue since I am not able to reproduce on any templates on both Node v4.4.5 & v6.1.0