@import "toolkit-no-css" generates compile error [#2259101]

I created a sub-theme in Omega 4 by running $ drush omega-wizard and carefully followed the instructions on https://drupal.org/node/1936970 to create a front-end development stack. But when I run $ bundle exec compass watch I get the error "File to import not found or unreadable: toolkit-no-css."

I have this in my [sub-theme].styles.scss:

// Import external libraries.
@import "compass";
@import "breakpoint";
@import "singularitygs";
@import "toolkit-no-css";

This is my Gemfile:

source 'https://rubygems.org'

group :development do

  # Sass, Compass and extensions.
  gem 'sass', '~>3.3.0'         # Sass.
  gem 'sass-globbing'           # Import Sass files based on globbing pattern.
  gem 'compass', '~>1.0.0.alpha.18'   # Framework built on Sass.
  gem 'compass-validator'       # So you can `compass validate`.
  gem 'compass-normalize'       # Compass version of normalize.css.
  gem 'compass-rgbapng'         # Turns rgba() into .png's for backwards compatibility.
  gem 'singularitygs', '~>1.2.0'   # Alternative to the Susy grid framework.
  gem 'toolkit', '~>2.0'        # Compass utility from the fabulous Snugug.
  gem 'breakpoint', '~>2.4'     # Manages CSS media queries.
  gem 'oily_png'                # Faster Compass sprite generation.
  gem 'css_parser'              # Helps `compass stats` output statistics.

  # Guard
  gem 'guard'                   # Guard event handler.
  gem 'guard-compass'           # Compile on sass/scss change.
  gem 'guard-shell'             # Run shell commands.
  gem 'guard-livereload'        # Browser reload.
  gem 'yajl-ruby'               # Faster JSON with LiveReload in the browser.

  # Dependency to prevent polling. Setup for multiple OS environments.
  # Optionally remove the lines not specific to your OS.
  # https://github.com/guard/guard#efficient-filesystem-handling
  gem 'rb-fsevent', :require => false                # Mac OSX

end

Any ideas why this is happening? I'm pulling my hair out!

Comments

Comment #1

kuremu commented 6 May 2014 at 08:02

I also have this problem. My guess is that the newer version of toolkit no longer includes toolkit-no-css. Presumably this functionality is replicated somewhere in toolkit or elsewhere, but I'm not sure where yet.

Also, if you have problems with the @import "border-box"; line in the normalize.scss file, replace it with @import "toolkit/kickstart";, which seems to do the same job. I figure there will be a similar solution with the toolkit-no-css issue (it's been renamed or moved somewhere else)

Comment #2

richardb88 commented 6 May 2014 at 13:20

Thanks, kuremu -- that makes sense. Changing @import "toolkit-no-css"; to @import "toolkit"; stops the error from showing, but I don't know if that's going to create other issues that haven't manifested yet.

Thanks too for the @import "toolkit/kickstart"; tip!

Comment #3

mrP commented 16 May 2014 at 01:33

One quick fix is to force toolkit 1.x in your Gemfile:

gem 'toolkit', '~> 1'

Not sure if this should be patched in to Omega 4.x or if there are plans to change the underlying toolkit import.

Comment #4

kjauslin commented 30 May 2014 at 12:19

The file _toolkit-no-css.scss is obsolete in toolkit 2.x. The box-sizing rules (previously excluded by using the no-css version) are now in the kickstart file. So, solution #1 is correct and makes completely sense.