0.5.1 • Published 5 years ago

import-resolve v0.5.1

Weekly downloads
16
License
MIT
Repository
github
Last release
5 years ago

import-resolve

resolve @import statements in css preprocessors

What this does

What if you have some less or stylus files that you want to smash together into a master file, without compiling to css? Just use import-resolve and all your dreams will come true. All @import statements will be resolved and you'll be left with one file containing all your precious mixins, variables and declarations.

Example:

// foo.less
@color_1: #444444;
@color_2: #555555;

// random-dir/bar.less
.mixin () {
    font-size: 16px;
}

// main.less
@import 'foo.less';
@import 'random-dir/bar.less';

#it-worked {
    color: green;
}

becomes...

@color_1: #444444;
@color_2: #555555;

.mixin () {
    font-size: 16px;
}

#it-worked {
    color: green;
}

Using import-resolve

npm install import-resolve
// some-node-thing.js
var importResolve = require('import-resolve');

// spits out a master dist file with all your wonderful stylesheet
// things concatenated
importResolve({
    "ext": "less",
    "pathToMain": "path/to/main.less",
    "output": "path/to/output.less"
});

// if you don't specify an output file, output accepts a callback parameter
// and passes the concatenated file text
var output = importResolve({
    "ext": "styl",
    "pathToMain": "path/to/main.styl"
}, function (output) {
    fs.writeFile('foo.styl', output, function (){
        console.log('did it myself.');
    });
});

// You can pass aliases if you have some files which have alias in your build process
importResolve({
    "ext": "less",
    "pathToMain": "path/to/main.less",
    "output": "path/to/output.less",
    "aliases": {
        "~myUniqueAlias": "path/to/unique/file.less"
    }
});

Using import-resolve from CLI

You can also use cli version of import resolve as described below.

import-resolve inputfile outputfile [extension]
  • first parameter is inputfile
  • second parameter is outputfile
  • third (optional) parameter is extension type (default is scss)

Tests

npm test

# Due to a bug in `jasmine-node`, Windows users should run: 
npm run-script win-test
0.5.0

5 years ago

0.5.1

5 years ago

0.4.0

9 years ago

0.3.0

9 years ago

0.2.8

9 years ago

0.2.7

9 years ago

0.2.6

10 years ago

0.2.5

10 years ago

0.2.4

10 years ago

0.2.3

10 years ago

0.2.2

10 years ago

0.2.0

10 years ago

0.1.0

10 years ago

0.0.4

10 years ago

0.0.3

10 years ago

0.0.2

10 years ago

0.0.1

10 years ago