No line number and file name of compile errors

Open
#50 3 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, ruby
Domain
tooling

Research direction

Reproduce the failure with bundle exec rake assets:precompile RAILS_ENV=production and the reported app/assets/javascripts/application.js, which uses require_tree .. Trace how the compile error is surfaced and make the completed error identify the JavaScript file and line where the recursion occurs.

Written by the indexing model from the issue text.

Description

When I try to precompile assets for production:

bundle exec rake assets:precompile RAILS_ENV=production
I get the following error:

ExecJS::ProgramError: RangeError: Maximum call stack size exceeded
(in /myapp/app/assets/javascripts/application.js)

This error is useless. It will be like finding a needle in a haystack. My application.js is simply one line which requires a bunch of other javascript:

 //= require_tree .

I need to know which file the infinite recursion occurs at and specifically what line number. Otherwise I can spend 2 months searching for this error. Surely, I am not the only person with this need. What kind I do in this situation?

Dominant language
Ruby
Stars
581
Forks
285
PR merge metrics
No merged PRs in 30d

Getting set up

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 rails/execjs

All issues in rails/execjs

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.