<commit_before># build-cli 0.3.4

*build-cli* allows you to manage your Electric Imp development from a command line through Electric Imp’s [Build API](https://electricimp.com/docs/buildapi).

# Installation

*build-cli* requires *node* and *npm* &mdash; see [Nodejs.org](https://nodejs.org/en/) for installation instructions. With *node* and *npm* installed enter the following:

```
npm install -g build-cli
```

# Usage

After installation, the `imp` program will be available from your command prompt. From there you should be able to use all of the tools (which are self documented as shown below).

```
imp [command] [options]

Commands:

    devices     List and manage devices
    log         Display logs from the specified device
    migrate     Migrates a model from one account to another
    models      List and manage models
    new         Create an new, empty imp project, or reinitialize an existing one
    pull        Fetch latest build from the server
    push        Update the build, and push code to developer devices
    setup       Sets your global Build API key
    help        Display help for [cmd]

Options:

    -h, help     output usage information
    -V, version  output the version number
```

# Introduction

In your home directory, run `imp setup` to set up your development environment. You will need a Build API key, which you can obtain by logging in to the [Electric Imp IDE](https://ide-electricimp.com/ide/) with your account credentials, and selecting ‘Build API Keys’ from the ‘username‘ menu on the top far right of the workspace.

Now you can create individual directories for each of your imp-based projects. To prepare a directory for use, change to the relevant directory and run `imp new`. You’ll be asked for a Build API key &mdash; just hit Enter to use the default value, the one you entered during the setup phase. Each project stores its own Build API key in addition to the global value stored during the setup process. This allows you to work on projects for other users, by entering a Build API key associated with their account when you run `imp new`, while also working on other projects of your own.

You will next be prompted for the name of the project. This can match an existing imp application (‘model’) or be entirely new if you want to create a project from scratch. You will also be asked to provide filenames &mdash; just hit Enter to use the default values &mdash; for your agent and device code files. These will be populated with the latest build from the Electric Imp impCloud&trade; if your project is derived from an existing model.

For further information, including a more detailed guide to using *build-cli*, please see [the Electric Imp Dev Center](https://electricimp.com/docs/buildapi/buildcli/).

# Release History

### 0.3.4

- Fix malformed dates in imp logs (thanks to @wcoole)

### 0.3.3

- Add spinning indicator to provide user with activity feedback during long server access calls.
- Improved table colouring.

### 0.3.2

- *log* bug fix

### 0.3.1
<commit_msg>Updated to v0.3.5<commit_after># build-cli 0.3.5

*build-cli* allows you to manage your Electric Imp development from a command line through Electric Imp’s [Build API](https://electricimp.com/docs/buildapi).

# Installation

*build-cli* requires *node* and *npm* &mdash; see [Nodejs.org](https://nodejs.org/en/) for installation instructions. With *node* and *npm* installed enter the following:

```
npm install -g build-cli
```

# Usage

After installation, the `imp` program will be available from your command prompt. From there you should be able to use all of the tools (which are self documented as shown below).

```
imp [command] [options]

Commands:

    devices     List and manage devices
    log         Display logs from the specified device
    migrate     Migrates a model from one account to another
    models      List and manage models
    new         Create an new, empty imp project, or reinitialize an existing one
    pull        Fetch latest build from the server
    push        Update the build, and push code to developer devices
    setup       Sets your global Build API key
    help        Display help for [cmd]

Options:

    -h, help     output usage information
    -V, version  output the version number
```

# Introduction

In your home directory, run `imp setup` to set up your development environment. You will need a Build API key, which you can obtain by logging in to the [Electric Imp IDE](https://ide-electricimp.com/ide/) with your account credentials, and selecting ‘Build API Keys’ from the ‘username‘ menu on the top far right of the workspace.

Now you can create individual directories for each of your imp-based projects. To prepare a directory for use, change to the relevant directory and run `imp new`. You’ll be asked for a Build API key &mdash; just hit Enter to use the default value, the one you entered during the setup phase. Each project stores its own Build API key in addition to the global value stored during the setup process. This allows you to work on projects for other users, by entering a Build API key associated with their account when you run `imp new`, while also working on other projects of your own.

You will next be prompted for the name of the project. This can match an existing imp application (‘model’) or be entirely new if you want to create a project from scratch. You will also be asked to provide filenames &mdash; just hit Enter to use the default values &mdash; for your agent and device code files. These will be populated with the latest build from the Electric Imp impCloud&trade; if your project is derived from an existing model.

For further information, including a more detailed guide to using *build-cli*, please see [the Electric Imp Dev Center](https://electricimp.com/docs/buildapi/buildcli/).

# Release History

### 0.3.5

- Retry logging after error

### 0.3.4

- Fix malformed dates in imp logs (thanks to @wcoole)

### 0.3.3

- Add spinning indicator to provide user with activity feedback during long server access calls.
- Improved table colouring.

### 0.3.2

- *log* bug fix

### 0.3.1

{'fraction_non_alphanumeric': 0.06306892067620286, 'fraction_numerical': 0.005851755526657998, 'mean_word_length': 3.5952203136669154, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4341674', 'n_tokens_mistral': 1595, 'n_tokens_neox': 1543, 'n_words': 909}