# Lock down sassc version

**URL:** https://meta.discourse.org/t/lock-down-sassc-version/101665
**Category:** Development
**Created:** [November 9, 2018, 1:43pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665 "2018-11-09T13:43:26Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Ori\_Pekelman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ori_pekelman/32/124402_2.png) [@Ori\_Pekelman](https://meta.discourse.org/u/Ori_Pekelman)
#### Post date: [November 9, 2018, 1:43pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/1 "2018-11-09T13:43:26Z")

</div>

Currently if you would `bundle update` you would end up with sassc (2.0.0) which breaks on precompiling assets with `Error: error C function image-url: initialised constant SassC::Script::String`

Locking down the sassc gem solves this issue.

`gem 'sassc', '~> 1.0', require: false`

I will try and figure out what breaks and get a solution for sassc ‘~\> 2.0’..

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 12, 2018, 7:00am UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/2 "2018-11-12T07:00:09Z")

</div>

I am definitely for the more ideal version of just figuring out how to upgrade sassc. PR totally welcome on that. It is going to be related to our sass customizations for themes and so on.

---

<div class="post-metadata">

### Author: ![bletch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bletch/32/69088_2.png) [@bletch](https://meta.discourse.org/u/bletch)
#### Post date: [November 26, 2018, 4:57pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/3 "2018-11-26T16:57:18Z")

</div>

> [@Ori\_Pekelman](#):
>
> gem ‘sassc’, ‘~\> 1.0’, require: false

Just ran across this myself in development mode with `git pull` and `bundle install`.

Thanks for the workaround.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 26, 2018, 9:37pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/4 "2018-11-26T21:37:17Z")

</div>

`bundle install` will certainly not cause it, `bundle update` will. I would like to get sassc upgraded though in Discourse that would be nice.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [March 20, 2019, 5:33pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/6 "2019-03-20T17:33:04Z")

</div>

Sassc is now updated

[https://github.com/discourse/discourse/commit/56b4ee43d3473601416a071c0afc185a8dc670de](https://github.com/discourse/discourse/commit/56b4ee43d3473601416a071c0afc185a8dc670de)

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [March 21, 2019, 6:00pm UTC](https://meta.discourse.org/t/lock-down-sassc-version/101665/7 "2019-03-21T18:00:11Z")

</div>

This topic was automatically closed after 24 hours. New replies are no longer allowed.