# grunt-browserify-alias

> Map paths to JS files and directories for use as aliases so that modules can be require'd without messy relative file paths.

Latest version **0.1.5** (published 2015-02-21) · 0 weekly downloads

> **Deprecated.** This package is deprecated.

## Install

```sh
npm install grunt-browserify-alias
pnpm add grunt-browserify-alias
yarn add grunt-browserify-alias
bun add grunt-browserify-alias
```

## Health

**Score 10/100 (F)** — status: deprecated.

Negative: deprecated.

## Facts

| | |
|---|---|
| Version | 0.1.5 |
| Published | 2015-02-21 |
| First published | 2015-02-20 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Node | >=0.8.0 |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Maintainers | munkychop |

## Links

- npm: https://www.npmjs.com/package/grunt-browserify-alias
- Repository: https://github.com/munkychop/grunt-browserify-alias
- Issues: https://github.com/munkychop/grunt-browserify-alias/issues
- npm.io page: https://npm.io/package/grunt-browserify-alias

## Recent versions

- 0.1.5 (latest) — 2015-02-21
- 0.1.4 — 2015-02-20

## README

### This module has been renamed and moved to a new repository:

**npm**
[https://www.npmjs.com/package/browserify-alias-grunt](https://www.npmjs.com/package/browserify-alias-grunt)

**Github**
[https://github.com/munkychop/browserify-alias-grunt](https://github.com/munkychop/browserify-alias-grunt)


Although this will remain here and continue to function in order to support legacy users, please start using **[browserify-alias-grunt](https://www.npmjs.com/package/browserify-alias-grunt)** instead.


---------------------------------------------------------

# grunt-browserify-alias
Map paths to JS files and directories for use as aliases so that modules can be require'd without messy relative file paths.

## Why use aliases?

You want to require modules from specific directories, without needing to use `../../../../some-module` to resolve relative paths.

For example, have a look at the following javascript directory structure:

```
root project directory
│
├──•Gruntfile.js
│
└───src
     │
     └───js
          │
          └───app
               │
               ├──• app.js
               │
               ├───controller
               │    │
               │    └──sunshine
               │       │
               │       └──• sunshine-controller.js 
               │
               └───model
                    │
                    └──sunshine
                       │
                       └──• sunshine-model.js 


```

Now, say we want to `require` *sunshine-model* from within the *sunshine-controller* module. The standard old crappy way to do this is:

```javascript
require("../../../model/sunshine/sunshine-model");
```

Now imagine that you refactor your code and modules get moved around. Suddenly, managing all those relative paths becomes even more of a pain in the butt.

Using *grunt-browserify-alias* at compile-time will allow you to `require` modules from the aliased directories you specify.

New hotness:

```javascript
require("model/sunshine/sunshine-model");
```

## Usage

### Installation

```
npm install --save-dev grunt-browserify-alias
```

### Implementation

Simply specify the files and directories you want to map by using a globbing pattern. Here is a very basic Gruntfile as an example:

```javascript
function Gruntfile (grunt)
{
    "use strict";

    var alias = require("grunt-browserify-alias");

    grunt.initConfig({

        browserify: {
            options : {
                alias: alias.map(grunt, {

                    // alias all js files in the 'app' directory
                    cwd: "src/js/app",
                    src: ["**/*.js"],
                    dest: ""
                })
            },

            src: "src/js/app/app.js",
            dest: "dist/js/app.js",
        },
    });


    grunt.loadNpmTasks("grunt-browserify");

    grunt.registerTask("default", ["browserify"]);
}

module.exports = Gruntfile;
```


It is also possible to specify multiple targets using an array of objects:

```javascript
function Gruntfile (grunt)
{
    "use strict";

    var alias = require("grunt-browserify-alias");

    grunt.initConfig({

        browserify: {
            options : {
                alias: alias.map(grunt, [
                    {
                        // alias app files
                        cwd: "src/js/app",
                        src: ["**/*.js"],
                        dest: ""
                    },
                    {
                        // alias lib files
                        cwd: "src/js/libs",
                        src: ["**/*.js"],
                        dest: ""
                    }
                ])
            },

            src: "src/js/app/app.js",
            dest: "dist/js/app.js",
        },
    });


    grunt.loadNpmTasks("grunt-browserify");

    grunt.registerTask("default", ["browserify"]);
}

module.exports = Gruntfile;
```

---
_Source: https://npm.io/package/grunt-browserify-alias · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._