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

The coffeescript compiler at 'coffee' is currently unavailable #12

Closed
xaviershay opened this issue Nov 16, 2010 · 6 comments
Closed

The coffeescript compiler at 'coffee' is currently unavailable #12

xaviershay opened this issue Nov 16, 2010 · 6 comments

Comments

@xaviershay
Copy link
Contributor

Upgraded to 0.6.0, get the following error in my server log, and no compilation:
The coffeescript compiler at 'coffee' is currently unavailable

It is available:
$ which coffee
/usr/local/bin/coffee

the preamble branch on my fork works for me. Won't get a chance to investigate until next week.

@stephencelis
Copy link

Same here.

@Sutto
Copy link
Owner

Sutto commented Nov 17, 2010

Odd - not sure what's going on here. Will take a look very shortly.

@nicolasblanco
Copy link
Contributor

I also had this problem. I installed Node+NPM via the official method in HOME (without sudo) :
https://gist.github.com/579814
and installed coffee-script via npm. and even if 'coffee' was in the PATH, Barista did not detect it.

I think that's because of the way barista detects coffee :
https://github.com/Sutto/barista/blob/master/lib/barista/compilers/node.rb#L8 :

using test -x will only return true if an absolute path to a file is given.

For example, testing on 'ls' returns false :

irb(main):001:0> system("test -x 'ls' >/dev/null 2>&1")
false

irb(main):003:0> system("test -x '/bin/ls' >/dev/null 2>&1")
true

So maybe you'll have to change this.
The workaround is to configure the full path in the configuration.
As I installed coffee via NPM in ~/local I added :

Barista.configure do |c|
  #...
  c.bin_path = File.expand_path("~/local/bin/coffee")
  # ...
end

@Sutto
Copy link
Owner

Sutto commented Nov 17, 2010

Oh wow, that's my mistake. Thanks for picking up that glaring oversight.

As a side note, I'm currently porting it across to use the Ruby coffee-script gem to avoid these issues / move that part of barista and that'll be done in the next 2-3 days

@Sutto
Copy link
Owner

Sutto commented Nov 22, 2010

I've just pushed 0.6.1 with a hopeful fix for this issue - can you guys take a look and confirm if it fixes it for you?

Re. the native version, slainer68's done a bunch of work and I'll be finishing up my work tomorrow as well so 0.7.0 isn't far off (since it introduces deprecated options).

Cheers

@xaviershay
Copy link
Contributor Author

0.6.1 fixes for me, thanks

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

No branches or pull requests

4 participants