You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.9.3-p392 :001 > require 'esprima'
=> true
1.9.3-p392 :002 > Esprima::Parser.new
TypeError: nil is not a symbol
from /Users/collins/.rvm/gems/ruby-1.9.3-p392@coffeebreak/gems/esprima-1.4.2/lib/esprima.rb:30:in `instance_variable_get'
from /Users/collins/.rvm/gems/ruby-1.9.3-p392@coffeebreak/gems/esprima-1.4.2/lib/esprima.rb:30:in `new_context'
from /Users/collins/.rvm/gems/ruby-1.9.3-p392@coffeebreak/gems/esprima-1.4.2/lib/esprima.rb:20:in `new_environment'
from /Users/collins/.rvm/gems/ruby-1.9.3-p392@coffeebreak/gems/esprima-1.4.2/lib/esprima/parser.rb:6:in `initialize'
from (irb):2:in `new'
from (irb):2
from /Users/collins/.rvm/rubies/ruby-1.9.3-p392/bin/irb:16:in `<main>'
The context seems to not include the expected stuff:
I'll take a look into this. Looks like Esprima is pulling the context out of ExecJS and passing it to CommonJS. But when ExecJS loads node.js, it doesn't have a "context" because it's an ExternalRuntime. Not sure this can be resolved.
Yeah, I fiddled with this a bit as well and couldn't figure it out. I believe there are a few similar issues filed against ExecJS, but no satisfactory answers yet :(
Sadness:
The context seems to not include the expected stuff:
🎷
The text was updated successfully, but these errors were encountered: