CodeKit - Bower

First Steps:: Getting Started; Live-Reload Browsers; Browser Sync; Set Language Options; Set Output Paths & Action

Second Steps:: Defaults For New Projects; Build Your Project; Set Target Browsers

Stuff To Know:: CodeKit + Git; Troubleshooting; License Recovery

PostCSS Tools:: Autoprefixer; PurgeCSS; CSSO; Custom PostCSS Plugins

Other Tools:: npm; Babel — (JS Transpiler); Terser — (JS Minifier); Rollup — (JS Bundler); Cache-Buster; HTML-Minifier; Bless

Languages:: Sass; Less; Stylus; JavaScript; CoffeeScript; TypeScript; Pug; Haml; Slim; Kit; Markdown; JSON

Image Optimizers:: WebP; PNG; JPEG; SVG; GIF

Frameworks:: CodeKit Frameworks; Tailwind; Bootstrap; Bourbon; Bitters; Zurb Foundation; Susy; Nib; Jeet

Syntax Checkers:: ESLint

Advanced:: Hooks; Environment Variables; Adding Custom Languages; Team Workflows; Scripting CodeKit

Editor Plugins:: Nova; Atom; Sublime Text; Coda 2

More: Read-Only Mode; Upgrading From 2.0; FAQ

Bower

Bower is a deprecated package-manager similar to npm. It is no longer actively developed and may be discontinued in the future.

CodeKit will support Bower as long as it exists. However, you should not use it for new projects.

Enabling Bower

a screenshot of the pop up button to switch between npm and bower in CodeKit

Open the Packages area in CodeKit. Switch to Bower by using the Registry PopUp Button shown in the sidebar when no packages are selected. Alternately, click the menu button to the right of the main search field.

Using Bower

The workflow for Bower packages is the same as that for npm, although some options are disabled because they aren't available in Bower.

For details, see the help page for npm.