bignimbus / import-resolve Goto Github PK

Hey,
Great repo, needed something like that for a long time.
Was just about to fix the issue when I import a file like so:

@import './bla';

but the actual file name is _bla.scss for instance and it couldn't find it, but found out it been fixed already (here).
Do you care to upload a new version to npm?
Thanks in advance.

For larger import trees, quite a lot of output is produced in the console. Can a quiet option or something be added to prevent the console statements from being spit out? Seems trivial...

I was hoping this script would resolve nested @import statements, that is, if I @import a file that contains an @import, I would expect that to be resolved as well.

Any plans for this?

When running the following script:

// stylus.js
var importResolve = require('import-resolve');
 
// spits out a master dist file with all your wonderful stylesheet 
// things concatenated 
importResolve({
    "ext": "styl",
    "pathToMain": "test.styl",
    "output": "dist/test.styl.css"
});

The colors used are not reset in the terminal:

As it is, there's too much repetition in declaring and resetting variables so that no information is persisted when using one instance of import-resolve to do multiple operations. We can cut this down by moving some functionality and settings to a constructor function.

I'm trying to concat bootstrap ( v4. alpha 5 )
giving main bootstrap file ( which imports all other mixins, vars etc )
this cause an infinitive loop,

to reproduce ..

in a new dir

npm install bootstrap@next ( which is v4. alpha5 currently )

importResolve({
"ext": scss,
"pathToMain": node_modules/bootstrap/scss/bootstrap.scss,
"output": ./out.scss
});