strarsis / sass-include-paths Goto Github PK

(self assigned)

Just took a two second look at your source and wondering if your code could be "easily" altered to be more generic by supporting generating an array of paths for any "main" file type? Pass in your file type and it returns array for same. Maybe as easy as generating your glob strings instead of hard coding them?

The stylus renderer works pretty much the same, taking an array of paths http://stylus-lang.com/docs/js.html

var sassFoldersGlobStr    = '{stylesheets,sass}';
var sassLibFoldersGlobStr = '{stylesheets,sass,lib,dist,assets/{sass,stylesheets},scss}';
var sassFilesGlobStr      = '*.{sass,scss}';
var sassGemsGlobStr = path.join('gems/*', sassFoldersGlobStr);

If this doesn't involve a major rewrite I could maybe do it as a fork with your input on the best way.

Here are some examples of popular bower components that are found using sassLibFoldersGlobStr but not using sassFoldersGlobStr:

• bower_components/bootstrap-sass/assets/stylesheets
• bower_components/font-awesome/scss

In truth, it would be nicest if there was some way that we could easily override the glob string in the opts argument.

I wrote a bower only version of this using wiredep but thought I would try this as it's a bit more flexible.

But the bowerComponents function is only returning paths of repos whose "main" key points to a file in a subdirectory of the repo.

For example if bower install "bemiby" it's main file is _bemify.scss in the root of that repo and your code does not add that to the array of paths.

Bower repos like "color-schemer" that have their "main" pointing to subdirectory like "/stylesheets" work fine.

here is my code.

paths: function(data) {
    Debug.L1("in sass paths function")

    let sass_paths = []
    .concat(sassIncl.bowerComponentsSync());
    Debug.L1('paths:\n' +  sass_paths);
    return sass_paths;

Expose the used glob strings so the user can easily change them.

Hello,

I'm facing an issue to run this command:

$ sassc $(sassIncludePaths --sassc --node_modules)  [...]
Internal Error: File to read not found or unreadable: [...]

Where can I fix it ?

Thanks