Current ExecJS runtime does't support ES6

Question

rake assets:precompile for my rails project throws below error:

rake aborted! Current ExecJS runtime does't support ES6. Please install latest Node.js.

Below is the environment information:

rails -v
Rails 5.0.7

ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]

node -v
v6.11.1

I tried reinstalling all my gems. But still, the error comes. OS is RHEL.

have you installed node.js already, which command you used. It's required to compile the Js code — Bijendra, Jul 17 '18 at 10:52
No we did not install node js. It came by default in the OS offering. OS is RHEL 7.2 — Vipul Kumar, Jul 17 '18 at 11:12

pfeffan · Answer 1 · 2018-07-17T16:24:10.120

19

i had the same problem after upgrading autoprefixer-rails to Version 9.0.0. i fixed it by setting autoprefixer-rails to a pre 9 version:

gem 'autoprefixer-rails', '8.6.5'

in my Gemfile

edited Jul 17 '18 at 16:24

answered Jul 17 '18 at 13:06

pfeffan

191
3

Same problem and solution using Rails 4.2 – Adrian Carr Jul 17 '18 at 18:15

score 11 · Answer 2 · answered Sep 21 '18 at 21:05

11

I had a similar problem after upgrading to Rails 5.2

The solution for me was to add this line

 # make the ExecJs use NodeJs
 ENV['EXECJS_RUNTIME'] = 'Node'

In this file

config/boot.rb

Then restart the rails server

answered Sep 21 '18 at 21:05

Ahmed Elkoussy

8,162
10
60
85

Thanks Quy, I am glad I could help :) – Ahmed Elkoussy Jan 09 '19 at 16:26

score 7 · Answer 3 · answered Jul 19 '18 at 16:05

7

Replace therubyracer by mini_racer in Gemfile:

# gem 'therubyracer', platforms: :ruby
gem 'mini_racer', platforms: :ruby

And then:

$ bundle install

answered Jul 19 '18 at 16:05

Caio Tarifa

5,973
11
46
73

score 5 · Answer 4 · answered Jul 17 '18 at 14:08

5

There's been a similar issue opened in the Autoprefixer-rails gem regarding this error, but it was thrown from an ActionView Template. keep an eye out for a response from the contributor:

https://github.com/ai/autoprefixer-rails/issues/137

answered Jul 17 '18 at 14:08

Kara Carrell

78
1
5

score -2 · Answer 5 · answered Dec 02 '20 at 15:16

-2

Installing NodeJS solved my problem.

answered Dec 02 '20 at 15:16

Touqeer Ijaz

15
2

This is not an answer, please consider leaving a comment instead. – Tyler2P Dec 02 '20 at 19:15

Current ExecJS runtime does't support ES6

5 Answers5