Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ExecJS Error

Open
#111 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
bootstrap, javascript, rails
Domain
frontend

Research direction

Reproduce Products#index with the gem installed and inspect application.html.erb, especially the stylesheet_link_tag and javascript_include_tag lines reported in the error. Determine why those asset tags trigger the ExecJS::ProgramError, then verify the error is resolved without removing the gem or either tag.

Written by the indexing model from the issue text.

Description

I have just installed this gem on my Rails project and I'm experiencing this error. I have tried to google it but have not found any useful info as to what is really causing it and the solution.

ExecJS::ProgramError in Products#index

Showing /home/ror/workspace/products/app/views/layouts/application.html.erb where line #7 raised:

TypeError: Cannot assign to read only property '__esModule' of #<Object>

Two lines in my application.html.erb are causing the error:
<%= stylesheet_link_tag 'application', media: 'all', 'data-turbolinks-track': 'reload' %>
<%= javascript_include_tag 'application', 'data-turbolinks-track': 'reload' %>

Commenting these lines or uninstalling the gem removes the problem but I don't think those are the right solutions.

Dominant language
SCSS
Stars
2k
Forks
437
Avg merge
1h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twbs/bootstrap-rubygem

All issues in twbs/bootstrap-rubygem

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.