Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
grunt-compass
Advanced tools
A custom grunt.js task that executes compass compile for you and prints the COMPASS output to grunt.log.write().
grunt-contrib-compass
FROM NOW ON.This is a custom grunt.js multitask aka gruntplugin that executes compass compile
on the command line for you and prints the COMPASS output to grunt.log.write()
.
You need to have node.js, grunt.js, Ruby, SASS and Compass installed for this to work.
Install this grunt plugin next to your project's grunt.js gruntfile with: npm install grunt-compass
.
Call grunt.loadNpmTasks( 'grunt-compass' )
in your gruntfile.
Configure grunt watch
to watch your scss files and call the task(s).
e.g.:
watch: {
files: [ 'assets/scss/*.scss' ],
tasks: [ 'compass:dev', 'compass:prod' ]
}
Setup your SASS and CSS paths
src: 'assets/scss',
dest: 'assets/css'
src
is the folder with sass or scss files and dest
is the folder where the css files will be placed.
Use specify
to specify certain files you want to compile:
A single file.
specify: 'assets/scss/base.scss'
Use globbing to match files, like:
specify: 'assets/scss/*.scss' // Match all scss files under `assets/scss` but not include files in subdirctory.
specify: 'assets/scss/**/*.scss' // Match all scss files under `assets/scss` include files in subdirctory.
See minimatch for more globbing usage.
Note a SASS/SCSS file will be ignored if its filename begin with an underscore _
. And all files you specify MUST be under the directory that you specified with src
.
See SASS-partials.
Use basePath
to specify the location in which to run Compass. Useful for when using grunt with multiple projects with seperate folder structures.
basePath: 'path/to/project/'
You can set your custom output style like this:
outputstyle: 'compressed'
You can disable line comments like this:
linecomments: false
If you have multiple compass tasks and you want to force compass compilation you can do this:
forcecompile: true
You can require ruby libraries before running commands like this:
require: 'animate-sass'
or
require: [
'animate-sass',
'mylib'
]
You can add the --debug-info
option for use with FireSass like so:
debugsass: true
You can set the relative assets to true
and set an image path for the Compass spriting feature:
images: '/path/to/images',
relativeassets: true
You can run compass with bundle exec if you need to as well:
bundleExec: true
If you have a Compass configuration file, you can use it instead of or in addition to the options in your gruntfile:
config: '/path/to/config'
If the path is not absolute, it is relative to the directory containing your gruntfile.
If you have a Compass configuration file, you set the environment variable for the config.rb file:
environment: 'production'
Then use it in your config.rb like so:
output_style = ( environment == :production ) ? :compressed : :expanded
You can add a custom IMPORT_PATH
folder, which makes files under the path findable by Sass's @import
directive:
importPath: '/path/to/importPath'
grunt compass-clean
Sometimes it can be faster to execute compass clean
and recompile for production instead of doing --force
compile.
Now grunt-compass comes with a grunt compass-clean
task that you can use when registering prod tasks in your gruntfile like:
grunt.registerTask( 'prod', [ 'compass-clean', 'compass:prod' ] );
Run "grunt watch" and edit some SASS files :)
compass: {
dev: {
src: 'assets/scss',
dest: 'assets/dev/css',
linecomments: true,
forcecompile: true,
require: [
'animate-sass',
'mylib'
],
debugsass: true,
images: '/path/to/images',
relativeassets: true
},
prod: {
src: 'assets/scss',
dest: 'assets/prod/css',
outputstyle: 'compressed',
linecomments: false,
forcecompile: true,
require: [
'animate-sass',
'mylib'
],
debugsass: false,
images: '/path/to/images',
relativeassets: true
}
}
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.
compass compile
configuration over here.v0.3.8: basepath option added.
v0.3.6: @shama added grunt v0.4 compatibility and the grunt-contrib style of structuring gruntplugins. Also: first tests!
v0.3.2: add support for IMPORT_PATH
v0.3.1: adds compiling of single files or a minimatch path via the src
option
v0.2.14: @nebelschwade added fonts-dir
option and fixed issue with config.rb due to changes in last version.
v0.2.13: Added grunt.template.process()
function to process src
and dest
paths. Suggested by @necolas in issue #9.
v0.2.12: The option to set the image path for spriting and the relativeassets to true have been added by @gcpantazis.
v0.2.11: @gcpantazis added the option to set the --debug-info
flag for Sass, useful for integration with the FireSass debugger.
v0.2.10: Added 'gruntplugin' as a keyword in the package.json to get listed here.
v0.2.9: Ability to require a given ruby lib before running commands. Added by @FGRibreau.
v0.2.8: Added an option to force compilation of SASS files via the --force
option.
Copyright (c) 2012 Kahlil Lechelt
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
A custom grunt.js task that executes compass compile for you and prints the COMPASS output to grunt.log.write().
We found that grunt-compass demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.