Bower 1.8.x: Main field precedence compatibility boundary remains undefined
Unresolved main field precedence in Bower 1.8.x When a package declares both main in bower.json and main in package.json , Bower 1.8.x exhibits ambiguous behavior in determining which file is authoritative for the dependency's entry point mapping. The Bower documentation states that main serves as a hint for file mapping, but does not specify a resolution or