We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the same way we have in webjars some features that could be ported to usage for bower :
The text was updated successfully, but these errors were encountered:
Thinking of this: a simple [[bower 'angular/angular.min.js']] could point to PROJECT_ROOT/bower_components/angular/angular.min.js
[[bower 'angular/angular.min.js']]
Sorry, something went wrong.
+1
On Sun, Apr 19, 2015 at 9:17 AM Jean-Laurent de Morlhon < [email protected]> wrote:
Thinking of this: a simple [[bower 'angular/angular.min.js']] could point to PROJECT_ROOT/bowercomponent/angular/angular.min.js — Reply to this email directly or view it on GitHub #48 (comment) .
Thinking of this: a simple [[bower 'angular/angular.min.js']] could point to PROJECT_ROOT/bowercomponent/angular/angular.min.js
— Reply to this email directly or view it on GitHub #48 (comment) .
Looking at the code it's not that easy to have a new directory not included in the default hard coded 'app' directory.
Maybe one way of doing it, is to add a .bowerrc like this, described in bower config:
.bowerrc
{ "directory": "app/bower_components" }
And have the bower handlebar helper points to it... but it's not ideal
No branches or pull requests
In the same way we have in webjars some features that could be ported to usage for bower :
The text was updated successfully, but these errors were encountered: