Skip to content

Instantly share code, notes, and snippets.

@theosp

theosp/issues-with-sass-and-meteor-v1.4.md

Created February 4, 2017 03:56
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save theosp/1906aaa1e0b46aa6ceaf5c6cd4f17ab7 to your computer and use it in GitHub Desktop.
Save theosp/1906aaa1e0b46aa6ceaf5c6cd4f17ab7 to your computer and use it in GitHub Desktop.
Download ZIP
Issues with Sass and Meteor v1.4
Raw
issues-with-sass-and-meteor-v1.4.md

Sass issues when migrating to Meteor v1.4

  1. Meteor v1.4 uses node v4
  2. fourseven:scss, the package that provides the sass compiler uses node-sass that uses libsass.
  3. Issues with libsass > v3.3 has issues with sass compilation in some edge case, fourseven:scss, falls on that edge case. (see this issue)
  4. libsass is a native node package, and as such need to be compiled (from c code) for the environment it's installed on.
  5. Starting from v1.4 Meteor moved the responsibility of compiling native dependencies from the package developer to the user.
  6. Any attempt to make meteor use a version compiled by me failed.
  7. I had to fine compiled sources
  8. [There were no compiled sources for libsass v3.2 for node v4. v3.2 is the last version that fourseven:scss used before moving to non sass supporting versions.
  9. But there were for v3.3.3, which is good as well
  10. From here the solution is obvious and I explained it here, but all the above had to be researched and understood for me to be able to come up with it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment