Unit tests requiring a JS file with public in its name are failing

[dpobel]

If a unit test HTML file requires a JS file with a path containing /public/, this JS file is not imported because Yeti tries to use its own file in this case and thus the test is likely to fail...
It seems like it is due to this route https://github.com/yui/yeti/blob/master/lib/hub/index.js#L345

[dpobel]

As I'm really annoyed by this issue, I'd like to provide a fix (or at least try to). On my setup, I have renamed the public folder in _public and have adapted the code in various places to match this rename.

Would a fix like this be sufficient or does it feel too much as a quick workaround ?

[reid]

Hey @dpobel, I'm writing a test to catch this bug. I think we can either fix the bad route regex or use an obnoxious name like __yeti__ instead of public that nobody will ever use.