Create an import map file with @import from a configured path
This plugin can be used with libsass, Ruby Sass, PostCSS or Less
Initially it's intend was to offer an alternative for Ruby Gem sass-globbing used with Ruby SASS
Supported CSS preprocessors
This plugin can be used with Ruby Sass as an alternative for the Ruby Gem
sass-globbing. It might increase speed on compile time but there is no comparison yet.
libsass (and Ruby Sass) do not support globbing out-of-the-box. This plugin helps you migrating existing projects from Ruby Sass to libsass.
With the release of v1.2.0 the generated @import map file is compatible with PostCSS.
As for the other CSS preprocessors, Less also supports the same type of @import statements, so you can configure this plugin to use it with Less.
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-sass-globbing --save-dev
The "sass_globbing" task
In your project's Gruntfile, add a section named
sass_globbing to the data object passed into
In this example, an import map from a defined path will be created. You can also ignore files, you will find details about the syntax at node-glob.
You should exclude the generated file from your version control system.
Usage with all options
Usage with CSS prepocessors other than Sass engines
If you want to use an other CSS preprocessor, just change the file extension from
.scss to the file extension supported by the preprocessor.
Determines whether single or double quotes are used around import statements.
false- Double quotes are used.
true- Single quotes are used.
/* generated with grunt-sass-globbing */\n\n
Sets the signature for the map files.
false- Disables adding of signature.
Usage in SCSS file
In this example, your file is located in src/screen.scss. This file imports the generated map files described iin the example Gruntfile above.
;;// more imports or rules
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
For detailed release information have a look at the change log