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
That said, it was @josh who implemented the "calling function in nested object"-feature in Duktape, so I believe the intention was to not support very complicated expressions in #call?
This repo seems pretty dead though, so the easiest fix is probably to change autoprefixer-rails.
I'm trying to use duktape with Rails environment:
After bundling gems I accessed the server and got
ExecJS::ProgramError : identifier '(function(opts) {return eval(process' undefined
.In autoprefixer-rails,
#call
was called with following contexts:In
ExecJS::DuktapeRuntime::Context#call
, it is parsed byidentifier.split(".")
. It results in wrongly splitted code.I don't know it is good to pass complex
identifier
for#call
, but the code written as such exists.The text was updated successfully, but these errors were encountered: