require.paths has been removed in node 0.6.x, I've commented out the unshift call, but I'm not sure what purpose that line was serving. If the unshift call is essential you may need to find a way to modify the NODE_PATH and spawn a new process instead...
check for node.js not just commonjs environment when including server…
don't use literal RegExp syntax for HCHARS because couchdb doesn't li…
…ke it for some reason
fix global variable leak
export optimizers in commonsjs environment too
Merge branch 'master' of https://github.com/akdubya/dustjs
require.paths has been removed in node 0.6.x, comment out unshift cal…
…l in lib/server.js
You guys do know that this project is probably dead so someone should maintain a fork instead?
It's a great nice awesome project, why it shall be dead? anyone can pinpoint any maintaned fork?
With require.paths commented out, seeing this error:
throw e; // process.nextTick error, or 'error' event on first tick
TypeError: Cannot call method 'runInNewContext' of undefined
at Object.loadSource (/Users/rich/dev/node_modules/dust/lib/server.js:13:19)
Apart from commenting out/removing the require.unshift line, the following change is needed:
-Script = process.binding('evals').Script;
+Script = require("vm");
This issue is 5 months old. Is this project dead ?
Is LinkedIn's fork basically the canonical version of dust.js now that the original can't run on current node?
can you update the npm script to pull dust.js from linkedin if that is official now?