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
So I added foundation as a dependency to my bower.json (so I can get the foundation.css file), and the angular-full-stack build automatically adds the foundation.js as a dependency. This causes my app to break due to conflicts.
Is there any way to prevent the injector from picking up a dependency in bower.json? In my case, I don't want foundation.js to automatically appear in the index.html which is generated by the build.
The text was updated successfully, but these errors were encountered:
Hi @mdedetrich,
You should be able to add an ignorePath option to the injector:js task. You could potentially be so vague as to say: ignorePath: '<%= yeoman.client %>/bower_components/**/foundation.js'
That is, if you didn't want to include any foundation.js file found anywhere in your bower_components folder.
Long story short, I am using https://github.com/madmimi/angular-foundation for my UI framework, and it requires the
foundation.css
file, but not thefoundation.js
file, to work.So I added
foundation
as a dependency to mybower.json
(so I can get thefoundation.css
file), and theangular-full-stack
build automatically adds thefoundation.js
as a dependency. This causes my app to break due to conflicts.Is there any way to prevent the injector from picking up a dependency in
bower.json
? In my case, I don't wantfoundation.js
to automatically appear in theindex.html
which is generated by the build.The text was updated successfully, but these errors were encountered: