Plans to move away from dynamic functions?

[jnarowski]

return pMatchFunctionCache[matcher] = new Function('el', source);

I'm not able to use this library in a serverless environment because of these dynamic functions. Any plans to refactor the code to not depend on these?

[ashi009]

Back to the time I wrote it, this was the fastest way to match nodes on a tree. Don't know if those assumptions are changed.

This can be replaced that with a closure with matching configs embedded.

[Tahiche]

This can be replaced that with a closure with matching configs embedded.
Can you explain how to do this?.

[jnarowski]

the new Function is now replaced and merged into master in this fork:
https://github.com/taoqf/node-html-parser