Skip to main content
tic2014
Participant
March 15, 2018
Answered

Error Compiling SASS in Dreamweaver - Rubygems unable to resolve dependency

  • March 15, 2018
  • 4 replies
  • 4040 views

I'm using an iMac with macOS High Sierra 10.13.3

In Dreamweaver CC 2018 18.1 when I save a SCSS file I get the following output error.

Red X,

Line: --,

Column:  1,

File:  stylesheet.scss

Error/Warning: /LibraryRuby/Site/2.3.0/rubygems/resolver.rb:231:in 'search_for'; Unable to resolve dependency: user requested "did_you_mean (= 1.0.0)' (Gem:unsatisfiableDependencyError)

Compiling was working for me earlier this week but Dreamweaver would freeze and crash about once and hour. (i use it 8+ hours a day). I updated dreamweaver and then the error happend.  I've reinstalled dreamweaver, installed/update xcode, updated Ruby, Gems, Homebrew, Rails.

Anyone know what could be causing the problem?

This topic has been closed for replies.
Correct answer Kratika Agarwal

Hi,

As Preran commented above that there isn't a way to set a custom path for Ruby in DW, but you can log this as an enhancement request Adobe Dreamweaver CC: Feature Ideas

Thanks

4 replies

Participant
May 22, 2018

Is there are definitive resolution for this issue? I'm experiencing exactly the same as detailed in the original post.

Preran
Community Manager
Community Manager
May 24, 2018

Hi Manojs,

Can you share your crash log files with Kratika?

Thanks,

Preran

Participant
May 11, 2018

Same issue here after an update of dreamweaver. I'm running the latest stable Ruby (2.5.1), latest sass (1.3.2) and running sass from the command line works.


The resolver.rb crashes on a dependency not met.

Is there a way to point dreamweaver to the external SASS compiler or to recreate the internal one. I already reset dreamweaver but this is getting annoying.

Preran
Community Manager
Community Manager
May 14, 2018

Did you try resetting preferences as requested by Kratika in her post?

Thanks,

Preran

Participant
May 14, 2018

Yes, I tried that as mentioned in my message.

After resetting Dreamweaver without success, I even went that far as remove dreamweaver from my Mac and remove all caches/p.lists/etc from my Mac, then reboot, followed by installing dreamweaver again.

My question is:

When dreamweaver is trying to compile an scss file, is it trying to use a build-in compiler or an external sass compiler? The error seems to be related to either a compiler not reporting back it's version number or even (I hope not) a version number required in the comments of the scss file.

And as a 2nd question, why not point Dreamweaver to Sass external? When in a terminal on my Mac I can use Sass without any issues. So why not point Dreamweaver to that binary?

regards

B i r n o u
Community Expert
Community Expert
March 22, 2018

you say that you have updated ruby, gems, homebrew, rails... but are you using Sass internally with DW, or externally using Ruby ?

I'm on windows, it happens sometime that I use bot (I mean DW compiling and Ruby externally)... I never encounter any trouble, but as I can see you're on Mac and I never tested such a context on this platform.

could you please confirm steps ? are you running DW compiler... or Ruby externally?... or both together ?

is it possible to get files for testing in a different platform ?

Community Manager
March 15, 2018

Hi,

Thanks for reporting, could you please share steps to reproduce the issue.

  • Is it happening for a new SCSS file created and saved.
  • Is there any specific option enabled in site setup-> CSS Preprocessor

Thanks

Kratika

tic2014
tic2014Author
Participant
March 19, 2018

The error occurs with new an existing SCSS files.

The only CSS Preprocessor setting enabled was "Enable Auto Compilation on File Save".

Now when I open Dreamweaver to use as a text editor, after about 5-10minutes of use it freezes and crashes. It's the only application running on my mac and I'm not performing any complex tasks.

Community Manager
March 22, 2018

Hi,

I am not able to reproduce the issue at my end.

Could you please try clearing DW preferences and see if the issue is resolved.

Unusual behavior in Dreamweaver? Try restoring preferences.

Thanks