You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all paths, e.g. ../bower_components/mocha/mocha.css are hard-coded and assume that Bower components reside at root level. In some cases though, this is not desired.
I'd suggest making paths dynamic with an option that would allow modifying Bower path.
Alternatively one could also identify if there's ../.bowerrc and fetch the path from there.
The text was updated successfully, but these errors were encountered:
Alternatively one could also identify if there's ../.bowerrc and fetch the path from there.
That's totally what we should do (but with bower.json). Using find-up, it should be fairly simple to locate the bower.json file and use it as the root where bower_components is located.
Currently all paths, e.g.
../bower_components/mocha/mocha.css
are hard-coded and assume that Bower components reside at root level. In some cases though, this is not desired.I'd suggest making paths dynamic with an option that would allow modifying Bower path.
Alternatively one could also identify if there's
../.bowerrc
and fetch the path from there.The text was updated successfully, but these errors were encountered: