Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirm support for various SCSS plugins #113

Closed
kennethormandy opened this issue Oct 5, 2013 · 4 comments
Closed

Confirm support for various SCSS plugins #113

kennethormandy opened this issue Oct 5, 2013 · 4 comments

Comments

@kennethormandy
Copy link
Collaborator

Most SCSS plugins are gems, but many of them are just wrapped that way and will actually work fine with Harp’s implementation of SCSS. I would like to confirm what will and won’t work, and hopefully get a jump on the documentation for it. @Apathetic012 asked:

Would it be possible to add support for compass plugins/configuration as well?

Yes, to a point. I’m running a version of Harp locally and using Compass, Susy and Stitch on my personal site and it works great.

I doubt anything will be built-in and Harp won’t support the proprietary features in these plugins, but the bulk of them are actually just SCSS. So, you should be able to drop them in, the same way you might for Bootstrap with LESS, or Nib with Stylus.

Here’s what should work fine upon SCSS getting added to Harp.

Supported

  • Compass Core (CSS3, Layout, Reset, Typography, Utilities)
  • Bourbon
  • Neat
  • Bitters (With @extends fall back)
  • Foundation Sass 4.3 Standalone
  • Foundation 5
  • Bootstrap-Sass

Unsupported

  • Compass Helpers, like generating sprites and the proprietary functions like image-width()
  • Susy, old version would work, but they switched to Sass 3.3. in the current beta
  • Stitch currently uses @extends, so it will work when libsass is updated
  • Anything else that is entirely proprietary functions, like modular-scale and SassyLists
  • Singularity and Breakpoint might work, but Team Sass seems committed to using bleeding edge Sass features, so it might not be worth porting it if that will change
@edrex
Copy link
Contributor

edrex commented Oct 27, 2013

What about Zurb Foundation?

@cyrusdavid
Copy link

as long as they support sass/scss you can unpack zurb-foundation and require the relative path.

@kennethormandy
Copy link
Collaborator Author

Thanks! I forgot to add that to the list. It was actually the first thing I tested, and it worked fine. I still need to check the Compass version, but if they are just using the mixins, I don’t see why that version wouldn’t work, too.

Also, some positive new on Compass becoming more modular.

@kennethormandy
Copy link
Collaborator Author

Here’s all the libraries that will presently work with Harp through libsass:

  • Compass Core (CSS3, Layout, Reset, Typography, Utilities)
  • Bourbon (v3.x)
  • Neat (Currently having problems, but there’s an open PR from us to fix it)
  • Bitters (With @extends fallback Should be fixed with the latest version of Harp)
  • Foundation 4.3.2 Sass Standalone
  • Foundation 5
  • Bootstrap-Sass

If you encounter a problem with a library you were hoping to use with Harp, please feel free to open a new issue and we’ll see what we can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants