Skip to content
Branch: master
Find file Copy path
Find file Copy path
5 contributors

Users who have contributed to this file

@chemzqm @timaschew @jonathanong @ericgj @tetsuo
239 lines (174 sloc) 7.64 KB

Getting Started: The Basics

Installing Component

First, you need to install node.js v0.10+. If you don't have it installed, visit node's download page.

Once installed, install Component from npm by running the following command:

$ npm install -g component

Using Component

The following is a quick introduction to Component through building a simple static site. It demonstrates the basic use of component for compiling local javascript and css files and remote css files.

Create index.html

First, create an empty directory, for intance my-first-component as our project root. Then create this file index.html in our project root:

<!DOCTYPE html>
    <title>Getting Started with Component</title>
    <link rel="stylesheet" href="build/build.css">
    <h1>My First Component</h1>
    <p class="blink">Woo!</p>
    <script src="build/build.js"></script>

You'll notice that we've linked to build/build.css and build/build.js files. This is where Component will build files to in the default case.

Create component.json

Let's create the component.json and set the name property.

  "name": "my-first-component"

Install a remote dependency

We want to include normalize.css, so let's install this remote dependency via the command: component install necolas/normalize.css. If you check the component.json file, you'll notice that component add the dependency automatically. You can also do it the other way: add a dependency, then run component install.

You should see this output on your stdout:

github remote: 54 of 60 requests remaining, resetting at Thu Oct 30 2014 00:23:36 GMT+0100 (CET)
github remote: see for more information.
   installed : necolas/normalize.css@3.0.2 in 283ms
     install : complete

We use necolas/normalize.css because that's where the code is hosted on GitHub.[1] If you don't specify any version via the command, component will install the latest version, which is 3.0.2 in this case. ^3.0.2 means that we want to use any version of normalize.css between 3.0.2 and below 4.0.0.[2]

Create index.css

Now, let's create a CSS file index.css. Let's reset the box model , to start:

* {
  box-sizing: border-box;

Create index.js

Now, let's create a JS file index.js that flashes the Woo! every 300 milliseconds in the HTML document.

var blink = document.querySelector('.blink');

setInterval(function () { = getComputedStyle(blink).visibility === 'hidden'
    ? 'visible'
    : 'hidden';
}, 300);

Add index.js and index.css to component.json

We need to add our files to the component.json, so it will end up looking like this:

  "name": "my-first-component",
  "dependencies": {
    "necolas/normalize.css": "^3.0.2"
  "scripts": ["index.js"],
  "styles": ["index.css"]

component build

Now, we run component build. You'll see an output like this:

$ component build
       build : resolved in 26ms
       build : files in 126ms
       build : build/build.js in 135ms - 4kb
       build : build/build.css in 130ms - 7kb

You'll see build/build.js and build/build.css files as referenced by index.html.

Open index.html

Run open index.html to open the the file in your browser. Now you'll notice that Woo! is flashing: the site is built.

Some observations

  • When you run component build, all dependencies (listed in component.json) will be installed automatically, as needed, and included in the build. (This behavior is different from previous versions of component, which split the install and build steps.)

  • In build/build.css, you'll notice that normalize.css is automatically included in the build first. Component concatenates CSS files in the following order: remote dependencies first, followed by local dependencies (i.e. listed in locals), followed by css files local to the component (i.e. listed in styles). For more info, see CSS Ordering.

  • The index.js will be loaded (required) automatically, so the text starts flashing immediately when you open the browser.

  • Note that box-sizing: border-box; is automatically prefixed with -webkit and -moz. Component uses the great autoprefixer by default to generate vendor prefixes.

Setup Authentication

You might noticed that Component prints a message if you run component install. It looks like this:

github remote: 54 of 60 requests remaining, resetting at Thu Oct 30 2014 00:23:36 GMT+0100 (CET)
github remote: see for more information.

GitHub provides 60 request per hour for an unauthenticated access. If you you need more, you need to use authentication. See changelog for more information.

Configuring GitHub access

Component 1.0.0 is using GitHub API to access GitHub repos, one simple way to configure your account is by adding global environment variable to your profile (eg: .bashrc r .zshrc) like this:

export GITHUB_USERNAME=<username>
export GITHUB_PASSWORD=<password>

One other secure way is by using GitHub oauth token instead of your password:

export GITHUB_USERNAME=<token>
export GITHUB_PASSWORD=x-oauth-basic

You can also use a .netrc file, add the following lines to your .netrc](

  login <token>
  password x-oauth-basic
  login <token>
  password x-oauth-basic

<token> is generated in the page, you can validate it via command:

Configuring bitbucket access

Component 1.0.0+ supports Bitbucket as a remote as well. The simplest way to support Bitbucket is to add globals to your profile (eg. .bashrc or .zshrc) like so:

export BITBUCKET_USERNAME=<username>
export BITBUCKET_PASSWORD=<password>

Additionally, you can add Bitbucket credentials directly to your .netrc file like o:

  login <username>
  password <password>

Currently, Bitbucket does not support generating a personal OAuth access token. The current documentation on OAuth with BitBucket only works with app authorization.

Next steps

If you want to learn different features of component step by step, you can try out the browse the c8-experiments repo.

There are also more examples.


[1] Component uses GitHub repos by default, but can be configured to use other remotes via custom adapters. See component/remotes.js for details.

[2] Component uses npm's semantic version string parser (node-semver).

You can’t perform that action at this time.