Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Bower introduction
Search
David DeSandro
October 12, 2013
Programming
2
1.2k
Bower introduction
What is Bower, why use it, and how I've been using it. Presented at ConvergeSE Richmond
David DeSandro
October 12, 2013
Tweet
Share
More Decks by David DeSandro
See All by David DeSandro
Read color hex codes
desandro
3
68k
Practical UI physics
desandro
3
1.5k
Other Decks in Programming
See All in Programming
CSC307 Lecture 06
javiergs
PRO
0
680
CSC307 Lecture 08
javiergs
PRO
0
660
責任感のあるCloudWatchアラームを設計しよう
akihisaikeda
3
160
AIと一緒にレガシーに向き合ってみた
nyafunta9858
0
160
OSSとなったswift-buildで Xcodeのビルドを差し替えられるため 自分でXcodeを直せる時代になっている ダイアモンド問題編
yimajo
3
600
Amazon Bedrockを活用したRAGの品質管理パイプライン構築
tosuri13
4
240
CSC307 Lecture 04
javiergs
PRO
0
650
フルサイクルエンジニアリングをAI Agentで全自動化したい 〜構想と現在地〜
kamina_zzz
0
400
HTTPプロトコル正しく理解していますか? 〜かわいい猫と共に学ぼう。ฅ^•ω•^ฅ ニャ〜
hekuchan
2
680
humanlayerのブログから学ぶ、良いCLAUDE.mdの書き方
tsukamoto1783
0
180
CSC307 Lecture 09
javiergs
PRO
1
830
AI によるインシデント初動調査の自動化を行う AI インシデントコマンダーを作った話
azukiazusa1
1
680
Featured
See All Featured
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.4k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
akashhashmi
0
270
Ethics towards AI in product and experience design
skipperchong
2
190
GraphQLの誤解/rethinking-graphql
sonatard
74
11k
Balancing Empowerment & Direction
lara
5
880
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Fantastic passwords and where to find them - at NoRuKo
philnash
52
3.6k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
Organizational Design Perspectives: An Ontology of Organizational Design Elements
kimpetersen
PRO
1
110
We Are The Robots
honzajavorek
0
160
エンジニアに許された特別な時間の終わり
watany
106
230k
Primal Persuasion: How to Engage the Brain for Learning That Lasts
tmiket
0
240
Transcript
Bower
We make websites
Lots of stuff Bootstrap Foundation normalize.css fitvid.js Modernizr d3 jQuery
Underscore / Lo-dash Backbone Angular JS Effeckt.css Masonry Font Awesome Compass H5BP jQuery UI Easing form gallery modal / popup tooltip base CSS helper JS
How do you get it? Download git clone Saved locally,
copy files
Where do you put it? lib/ lib/vendor/ assets/js/vendor, assets/css/vendor,
assets/*/vendor
How you keep track of it? Centralized server In git,
commit to repo git-submodules
Lots of stuff Bootstrap Foundation normalize.css fitvid.js Modernizr d3 jQuery
Underscore / Lo-dash Backbone Angular JS Effeckt.css Masonry Font Awesome Compass H5BP jQuery UI Easing form gallery modal / popup tooltip base CSS helper JS
None
Messy Desk Not enough space to do work Slow down
creative process Hard to collaborate Spend time cleaning desk
Package Management
Lots of stuff Bootstrap Foundation normalize.css fitvid.js Modernizr d3 jQuery
Underscore / Lo-dash Backbone Angular JS Effeckt.css Masonry Font Awesome Compass H5BP jQuery UI Easing form gallery modal / popup tooltip base CSS helper JS
Package Management
Problem Package management Solution Bower Reason Why use Bower Results
How I’ve done so far
What is Bower?
Bower A package manager for the web
What is Bower? Command-line utility Built on Node JS
Install packages bower install jquery
None
Install a version bower install jquery#1.x
None
Search packages bower search normalize
None
bower.json Manifest file Use same installation on another machine Collaboration
bower.json bower init
None
bower.json "dependencies": { "jquery": "1.x", "normalize-‐css":
"~2.1.3" }
bower install bootstrap
None
Installing dependencies Bower will install the package and its dependencies
!"# bootstrap#3.0.0 !"" jquery#2.0.3
Dependencies Powerful feature Build packages on top of one another
No longer have to depend on big frameworks
Lots of other great features --offline: Offline mode Read the
docs: bower.io
What Bower does Easily gets packages Keeps them organized Manages
dependencies
Problem Solution Reason Results Package management Bower Why use Bower
How I’ve done so far
Why Bower?
Package managers Volo git-submodules Jam Component Browserify (npm) Ender
Bower is special Unopinionated Provides no direct way to consume
packages Core part of its philosophy
Consuming packages <link />, <script /> SASS or preprocessor RequireJS
Grunt Your own build script
bower list -‐-‐paths { "bootstrap": [
"bower_components/bootstrap/dist/js/ bootstrap.js", "bower_components/bootstrap/dist/css/ bootstrap.css" ], "jquery": "bower_components/jquery/jquery.js", "normalize-‐css": "bower_components/normalize-‐ css/normalize.css" }
Unopinionated Choosing on behalf of anyone else Don’t lock your
users into a methodology
Using Bower Twitter: Flight Google: Yeoman, Angular jQuery
Problem Solution Reason Results Package management Bower Unopinionated How I’ve
done so far
Results
Isotope Masonry
Same problem with unloaded images
Masonry ! Isotope !
Masonry ! Isotope ! images Loaded images Loaded images Loaded
Masonry ! Isotope ! images Loaded images Loaded images Loaded
Maintaining one project in three places
Now with Bower No more committing other projects into yours
Keep them separated Bower allows easily add them as dependencies
Front-end development with dependencies
Developing with dependencies Removing duplicated code jquery-bridget get-size get-style-property doc-ready
eventie EventEmitter
Each dependency Its own repository Its own issue tracker Its
own tests Finer granularity over bigger projects
For example: masonry#417
masonry#417 Issue reported in Masonry Actual problem with getSize
getSize Fix cut new release (v1.1.5) Masonry bower update deploy
Masonry ! getSize Isotope ! Dragga- billy ...
Encapsulation Literal naïve definition: Make capsules Breaking down something large
into smaller pieces, easier to swallow
Encapsulation Like DRY, a principle of good programming Take and
apply it project-level
Encapsulation A new avenue of thinking No longer had to
keep mental model of entire library in my head Focus on small libraries with single purpose
Growing up Growing out of relying on monolithic frameworks Empowering
developers to make and distribute their own purpose- built components
packery-‐docs#1.0.0 $"" classie#1.0.0 $"# doc-‐ready#1.0.2 % !""
eventie#1.0.3 $"# draggabilly#1.0.6 % $"" classie#1.0.0 % $"" eventEmitter#4.2.4 % $"" eventie#1.0.3 % $"# get-‐size#1.1.4 % % !"" get-‐style-‐property#1.0.2 % !"" get-‐style-‐property#1.0.2 $"" eventie#1.0.3 $"" get-‐style-‐property#1.0.2 $"" jquery#1.10.2 $"" jquery-‐ui-‐draggable#1.10.3 $"" normalize-‐css#2.1.3 !"# packery#1.1.2
Problem Solution Reason Results Package management Bower Unopinionated Grow
How? How do you hook up Grunt tasks to Bower?
How do you split a project into multiple files? How do you make JS work with both RequireJS and <script />? How do you create concatenated source files, for easy <link />ing?
Why use Bower and not ______? Because Bower is unopinionated.
Why use Bower at all? Because building with dependencies
is how we will grow.
Thank you! I have stickers. Get in my van. –
@desandro